Initial dynamic element template value is not pre-populated.

Describe the bug

Related to https://github.com/camunda/camunda-modeler/issues/3029 whenever I initially apply an element template the initial value is not applied.

Steps to reproduce

Consider following element template and video attached (works in web modeler and Desktop Modeler (nightly)):

https://user-images.githubusercontent.com/108870003/204857843-927b9ffe-d4e2-4f15-8478-0a7896ba42de.mov

Element template attached below ⬇️.

Expected Behavior

When initially applying an element template with a dynamic binding the valid effects (for which the condition is true) is applied.

Additional Context

Element template to reproduce this:

{
  "$schema": "https://unpkg.com/@camunda/zeebe-element-templates-json-schema/resources/schema.json",
  "name": "dynamic-values",
  "id": "2b9dc4da-6acc-478c-a774-ece1b04ff988",
  "appliesTo": [
    "bpmn:ServiceTask"
  ],
  "properties": [
    {
      "id": "default-changer",
      "label": "Change the default",
      "type": "Dropdown",
      "choices": [
        {
          "name": "Set it as 1",
          "value": "set-1"
        },
        {
          "name": "Set it as 2",
          "value": "set-2"
        },
        {
          "name": "Set it as 3",
          "value": "set-3"
        }
      ],
      "binding": {
        "type": "zeebe:input",
        "name": "ignore"
      },
      "constraints": {
        "notEmpty": true
      }
    },
    {
      "label": "Test",
      "type": "String",
      "value": "1",
      "binding": {
        "type": "zeebe:input",
        "name": "test"
      },
      "condition": {
        "property": "default-changer",
        "equals": "set-1"
      }
    },
    {
      "label": "Test",
      "type": "String",
      "value": "2",
      "binding": {
        "type": "zeebe:input",
        "name": "test"
      },
      "condition": {
        "property": "default-changer",
        "equals": "set-2"
      }
    },
    {
      "label": "Test",
      "type": "String",
      "value": "3",
      "binding": {
        "type": "zeebe:input",
        "name": "test"
      },
      "condition": {
        "property": "default-changer",
        "equals": "set-3"
      }
    }
  ]
}

_Originally posted by @igpetrov in https://github.com/camunda/camunda-modeler/issues/3029#issuecomment-1332453030_

---

Depends on https://github.com/camunda/camunda-modeler/issues/3327.

[smbea]

I have a fix for this issue if this is the route we want to go https://github.com/bpmn-io/bpmn-js-properties-panel/pull/824. It also aligns the behaviour with zeebe:property

[nikku]

As discussed @smbea can you take this one over?

I root caused it and from what it seems like we don’t properly initialize zeebe:input bindings (https://github.com/camunda/camunda-modeler/issues/3327#issuecomment-1333362385).