Feature Request: Component Mapping Option During Import and Shared App Installation

We need a way to map components when importing a flow or application into the hub. When a flow is imported, the system should provide an option that allows the user to map the imported component to an existing component in the hub.

During the import process, the user should be able to choose whether to:

Map the component to an existing component, or

Import the component as a new component, even if a component with the same name already exists.

This option should always be presented to the user so they can explicitly decide how the component should be handled. This will give users better control over component reuse and help prevent unintended overwriting or duplication.

Additionally, the same functionality should be available when using the shared application feature. When a user shares a URL for an app with another organization, the receiving user can use that URL to import the app into their environment. During this import process, the system should also allow the user to map the components used by the shared app to existing components in their environment, or choose to import them as new components.

This ensures consistent behavior across both direct imports and shared app installations, while giving users flexibility to reuse existing components in their organization.