Deploy multiple instance of the same application in collections

[QuentinBisson]

Is your feature request related to a problem? Please describe. Coming from https://gigantic.slack.com/archives/C02GDJJ68Q1/p1726752552645969, in atlas, we need to be able to deploy the alloy app as alloy-gateway because we use this app in multiple instances. I'm currently frustrated because our tooling is too opinionated and does not allow it.

@uvegla started to work on it in March of this year https://github.com/giantswarm/architect-orb/pull/511/files and that works for pushing the app to the collection but the app cannot be pulled because konfigure expects the config to be for the app named alloy when it should be using the app deployed name and not the app name in the catalog.

Describe the solution you'd like I would like to be able to set the deployed app name like https://github.com/giantswarm/architect-orb/pull/511/files and be able to have a config in shared-config using the deployed-app-name and not the name of the app in the catalog.

Describe alternatives you've considered Deploy the app with the other name in the catalog but uhhhg

Additional context This is currently blocking https://github.com/giantswarm/roadmap/issues/3568 from going forward

[weatherhog]

we in Honeybadger need to do some more investigation on this topic. @uvegla did some initial work but is on vacation. @uvegla could you please add your thoughts when you are back.

[uvegla]

If I remember correctly that orb change is not enough. konfigure also needs to change and thus generators and maybe all the collections and related tools (e.g. the automation that updates app versions in collections). Not to mention vintage and config-controller if we still need to care about that here. It is potentially a quite significant change.

[QuentinBisson]

So I managed to make this run until the konfigure step with this PR. I have no clue what the impact would be there but we definitely do not need to care about vintage here