Option to change appName when duplicating services

What problem will this feature address?

When duplicating services to another project or environment, the duplicated services keep the same appName as the original ones.

This makes it inconvenient to manage multi-environment setups (e.g. staging, production, preview) where different naming conventions are required, and it increases the amount of manual work needed after duplication.

Describe the solution you'd like

When duplicating one or more services, provide an optional way to change the appName of each duplicated service during the duplication process.

This could be implemented in different ways, for example:
• Allow editing the appName per service before confirming duplication
• Any simple mechanism that enables renaming at duplication time

The feature should be optional so the current behavior remains unchanged if no modification is needed.

Describe alternatives you've considered

Duplicating services and manually renaming each name afterward
→ This changes the name, but not the appName.

Maintaining separate templates or recreating services manually
→ This adds unnecessary overhead and defeats the purpose of service duplication.

Additional context

No response

Will you send a PR to implement it?

No

Start by locating the service-duplication flow and the code that handles appName values. Trace how duplicated services are presented and created, then define a small optional input for renaming each service while confirming that unchanged duplication preserves current behavior.