Bean configuration UI

[igarashitm]

Please describe the feature that you want to propose

While beans support at source code level is to be added soon #1721
We also need to design how to let users configure those beans in Kaoto. Since beans is not a part of the flow, we need a separate view for configuring it apart from the flow graph as a tree of steps. We start from beans, but there're other type of "out of the flow" objects that could be defined in the Camel Route, such as error-handler and on-exception.

Possible targets

Camel Route

• beans
• error-handler
• on-exception
• routes
• camel-context
• ...

Kamelet

• /spec/template/beans

Integration

• /spec/flows/beans

---

Related issue about adding contextual endpoint for specific DSLs: KaotoIO/kaoto-backend#657

[igarashitm]

Camel Route, Kamelet and Integration uses same schema for beans

Schema

{
  "title": "Beans",
  "description": "Beans Configuration",
  "type": "array",
  "items": {
    "type": "object",
    "additionalProperties": false,
    "properties": {
      "name": {
        "type": "string"
      },
      "type": {
        "type": "string"
      },
      "properties": {
        "type": "object"
      },
      
    },
    "required": [
      "name",
      "type"
    ]
  }
}

Compatibility issue: key/value style property on Kamelet and Integration

Although it is against schema, runtime allows key/value style of beans property. Even official Kamelets use this style ATM.
apache/camel-kamelets#1475

      - name: dsBean
        type: "#class:org.apache.commons.dbcp2.BasicDataSource"
        property:
          - key: username
            value: '{{username}}'
          - key: password
            value: '{{password}}'

We might go with what schema allows at a first step, then consider loading this old style property and convert to the valid one.
Unfortunately it turned out the object type of properties doesn't work on Kamelet on Camel3. Runtime and schema are out of sync.
https://github.com/apache/camel/blob/camel-3.x/dsl/camel-yaml-dsl/camel-yaml-dsl-deserializers/src/main/java/org/apache/camel/dsl/yaml/deserializers/BeanFactoryDefinitionDeserializer.java#L61

so at least for Camel3 Kamelet, we have to support key/value style.