When a service is duplicated across multiple environments and then renamed in one environment, the duplicated service in the other environment is also renamed unexpectedly.

Steps to Reproduce:

1. Create a service in the production environment (e.g., ogogo-api)
2. Duplicate this service to another environment (e.g., t4-staging)
3. In the production environment, rename the service (e.g., from ogogo-api to ogogo-api)
4. Check the staging environment

Expected Behavior:

The service in the staging environment should remain unchanged with its original name. Services in different environments are independent and should not be affected by changes to services in other environments.

Actual Behavior:

The duplicated service in the staging environment is automatically renamed as well (e.g., from t4-ogogo-api to ogogo-api), even though it's in a completely separate environment.

Environment Details:

• Multiple environments affected (production and staging)
• Service was duplicated using Railway's duplication feature
• Both services deploy from the same GitHub repository

Impact:

This creates confusion and unintended side effects when managing services across environments, as changes to one environment unexpectedly cascade to others.