Description

As a user, when creating an source for kamelets, I should be presented with a form/yaml view and ability to switch between two

Acceptance Criteria

1. on route based on catalog , i.e catalog/event-source?sourceType=kamelet&name=telegram ... user should be able to see view as we have for builderImages/helm
2. Based on queryParam above required source form/yaml along with icon and description should be shown to user
3. Check for icon in data if Icons are not present  we need to use from code as we do now and if not known show user with default icon
4. If JsonSchema is present show spec properties based on that along with sink form section and application name section with yaml Switcher as well
5. If JsonSchema is present show generic fields i.e application name, group and Sink
6. Handle error scenario for form yaml switching

Additional Details:

Proposal doc : https://docs.google.com/document/d/1vwnJh8kZTPreAQ4fWT-SJg3JiFKE215ovFZ-pCf0pkA/edit#heading=h.rjrkctmedt3u 

Can leverage https://github.com/openshift/console/blob/master/frontend/packages/console-shared/src/components/formik-fields/SyncedEditorField.tsx 

Kameltes : https://github.com/openshift-integration/kamelet-catalog