fix: KaotoIO#1030

fix: KaotoIO#1030

fix: KaotoIO#1030

fix: KaotoIO#1030

In order to create new entities, a DSL Slector component needs to be
added.

This commit adds said component divided in 3 sections:

1. `ChangeDSLModal`: A modal to warn the user whenever the DSL is being
   changed since the existing integration will be removed
2. `DSLSelectorToggle`: The DSL Button itself
3. `DSLSelector`: The main entrypoint for the DSL Selector, this
   component is in charge of combining both `DSLSelectorToggle` and the
`ChangeDSLModal` components

relates: KaotoIO#1030

With the upcoming rework on the New Flow aspect of Kaoto, the existing
functionality will be only used in the Empty State, therefore, we're
moving those files to be a subcomponent of said component.

relates: KaotoIO#1030

In order to create new entities, a DSL Slector component needs to be
added.

This commit adds said component divided in 3 sections:

1. `ChangeDSLModal`: A modal to warn the user whenever the DSL is being
   changed since the existing integration will be removed
2. `DSLSelectorToggle`: The DSL Button itself
3. `DSLSelector`: The main entrypoint for the DSL Selector, this
   component is in charge of combining both `DSLSelectorToggle` and the
`ChangeDSLModal` components

relates: KaotoIO#1030

In order to create new entities, a DSL Slector component needs to be
added.

This commit adds said component divided in 3 sections:

1. `ChangeDSLModal`: A modal to warn the user whenever the DSL is being
   changed since the existing integration will be removed
2. `DSLSelectorToggle`: The DSL Button itself
3. `DSLSelector`: The main entrypoint for the DSL Selector, this
   component is in charge of combining both `DSLSelectorToggle` and the
`ChangeDSLModal` components

relates: KaotoIO#1030

fix: KaotoIO#1030

In order to simplify the construction of new entities, we need to
provide a default parameter to the constructor, so the entities can be
created on its own.

Related entities:
* ErrorHandler
* Intercept
* InterceptFrom
* InterceptSendToEndpoint
* OnCompletion
* OnException
* RestConfiguration
* RouteConfiguration

relates: KaotoIO#1030

With the upcoming rework on the New Flow aspect of Kaoto, the existing
functionality will be only used in the Empty State, therefore, we're
moving those files to be a subcomponent of said component.

relates: KaotoIO#1030

In order to create new entities, a DSL Slector component needs to be
added.

This commit adds said component divided in 3 sections:

1. `ChangeDSLModal`: A modal to warn the user whenever the DSL is being
   changed since the existing integration will be removed
2. `DSLSelectorToggle`: The DSL Button itself
3. `DSLSelector`: The main entrypoint for the DSL Selector, this
   component is in charge of combining both `DSLSelectorToggle` and the
`ChangeDSLModal` components

relates: KaotoIO#1030

fix: KaotoIO#1030

In order to simplify the construction of new entities, we need to
provide a default parameter to the constructor, so the entities can be
created on its own.

Related entities:
* ErrorHandler
* Intercept
* InterceptFrom
* InterceptSendToEndpoint
* OnCompletion
* OnException
* RestConfiguration
* RouteConfiguration

relates: #1030

In order to create new entities, a DSL Slector component needs to be
added.

This commit adds said component divided in 3 sections:

1. `ChangeDSLModal`: A modal to warn the user whenever the DSL is being
   changed since the existing integration will be removed
2. `DSLSelectorToggle`: The DSL Button itself
3. `DSLSelector`: The main entrypoint for the DSL Selector, this
   component is in charge of combining both `DSLSelectorToggle` and the
`ChangeDSLModal` components

relates: #1030

With the upcoming rework on the New Flow aspect of Kaoto, the existing
functionality will be only used in the Empty State, therefore, we're
moving those files to be a subcomponent of said component.

relates: #1030

fix: KaotoIO#1030

fix: KaotoIO#1030

fix: KaotoIO#1030

fix: KaotoIO#1030

fix: KaotoIO#1030

fix: KaotoIO#1030

fix: KaotoIO#1030

fix: KaotoIO#1030

fix: KaotoIO#1030

Currently, setting the current DSL and creating a new entity are tied
together in a single step in the NewFlow component.

This commit split that functionality in two separate buttons:
1. DSL Selector: Meant to choose the current DSL and therefore determine
   which type of entities can be added into the Canvas
2. NewEntity: This is for adding new entities, supported by the current
   DSL, or said in a different way, allows to add entities from the
current CamelResource registry.

The existing functionality from the CanvasEmptyState is preserved for
now.

In addition to that, when removing all routes, a new route won't be
created by default.

fix: KaotoIO#1030

Currently, setting the current DSL and creating a new entity are tied
together in a single step in the NewFlow component.

This commit split that functionality in two separate buttons:
1. DSL Selector: Meant to choose the current DSL and therefore determine
   which type of entities can be added into the Canvas
2. NewEntity: This is for adding new entities, supported by the current
   DSL, or said in a different way, allows to add entities from the
current CamelResource registry.

The existing functionality from the CanvasEmptyState is preserved for
now.

In addition to that, when removing all routes, a new route won't be
created by default.

fix: KaotoIO#1030

Currently, setting the current DSL and creating a new entity are tied
together in a single step in the NewFlow component.

This commit split that functionality in two separate buttons:
1. DSL Selector: Meant to choose the current DSL and therefore determine
   which type of entities can be added into the Canvas
2. NewEntity: This is for adding new entities, supported by the current
   DSL, or said in a different way, allows to add entities from the
current CamelResource registry.

The existing functionality from the CanvasEmptyState is preserved for
now.

In addition to that, when removing all routes, a new route won't be
created by default.

fix: KaotoIO#1030

Currently, setting the current DSL and creating a new entity are tied
together in a single step in the NewFlow component.

This commit split that functionality in two separate buttons:
1. DSL Selector: Meant to choose the current DSL and therefore determine
   which type of entities can be added into the Canvas
2. NewEntity: This is for adding new entities, supported by the current
   DSL, or said in a different way, allows to add entities from the
current CamelResource registry.

The existing functionality from the CanvasEmptyState is preserved for
now.

In addition to that, when removing all routes, a new route won't be
created by default.

fix: KaotoIO#1030

Currently, setting the current DSL and creating a new entity are tied
together in a single step in the NewFlow component.

This commit split that functionality in two separate buttons:
1. DSL Selector: Meant to choose the current DSL and therefore determine
   which type of entities can be added into the Canvas
2. NewEntity: This is for adding new entities, supported by the current
   DSL, or said in a different way, allows to add entities from the
current CamelResource registry.

The existing functionality from the CanvasEmptyState is preserved for
now.

In addition to that, when removing all routes, a new route won't be
created by default.

fix: #1030