Creation of kamelets via Event Source Creation mechanism

Description

As we introduce more camel connectors, we will need to handle scaling of these connectors as event sources. In our current Event Source creation experience, we provide a small list of tiles for the user to pick from. This presentation won't scale as more connectors/ event sources are provided. Along with scalability we would as well need better experience for users to be shown with Form/yaml view while creation of these connectors.

Goal

Goal is to have Camel Connectors as event sources available in the Developer Catalog and have form/yaml view for the supported connectors

Acceptance criteria:

If the Serverless operator is not installed ...

1. As a user, I should not see "Event Source" card on the +Add page or any menus
2. As a user, I should not see an "Event Source" type filter in the Developer Catalog

If the Serverless operator/ Knative Camel operator is installed ...

1. As a user, when clicking on Dev Catalog from +Add page, I should see available Camel connectors / event sources among other items
2. As a user, when clicking on Dev Catalog from +Add page, I should see a "Event Source" type filter to allow me to get a more contextual experience around Event Sources
3. As a user, I should see "Event Source" card on the +Add page and on menus
4. As a user, when clicking on the "Event Source" card on the +Add page or menus, I should get a more contextual experience around available Camel connectors / Event Sources
5. When in this contextual experience around Camel Connectors/Event Sources, I should be able to filter by Event Source type. Work with the MW team to determine if we need "Camel Connectors"
6. As a user i should see respective icons along with description for camel Connectors
7. As a user i should be able to create camel connectors of type AWA /Azur/Slack etc
8. As a user, when creating an camel connectors, I should be presented with a form
9. As a developer, I should be able to freely switch between form and YAML editor without losing changes

Dependencies (External/Internal):

Design Artifacts:

Notes

• Work with the MW team to determine the contract how will these (json schema/Descriptors/icons/Description) be provided with Kamelets
• Work with the MW team to determine if we need "Connectors" and/or "kamelets"
• As forms would be dynamic so supporting custom components would be an iterative process. Can see currently set of components supported as descriptors here https://github.com/openshift/console/blob/master/frontend/packages/operator-lifecycle-manager/src/components/descriptors/reference/reference.md