The "app link" command is limited to one app per environment per team

Description

The app link command is limited to one app per environment (local or deployed) per team, which limits the development "stages" that might exist:

• Development
• Staging
• Production

At the moment this is expected behavior:

Only one app can exist for each combination of Team ID and environment.

📚 https://docs.slack.dev/tools/slack-cli/reference/commands/slack_app_link/

Version

Using slack v3.10.0

Steps to reproduce:

1. Create multiple apps for a team on api.slack.com/apps
2. Run the app link command in a project using these app IDs
3. Find that one app can exist for development purposes

Expected result:

Multiple apps to be saved for later selections:

$ slack deploy
? Select an app
  A0101010101 slackbox-ez T0000000001 (production)
> A0000000001 tinyspeck T0123456789 (production)
  A0123456789 tinyspeck T0123456789 (staging)

Actual result:

$ slack app link
...

🚫 A saved app was found and cannot be overwritten (app_found)

💡 Suggestion
   Remove the app from this project or try again with --force

Requirements

• I've read and understood the Contributing guidelines and have done my best effort to follow them.
• I've read and agree to the Code of Conduct.
• I've searched for any related issues and avoided creating a duplicate issue.

Start by tracing the app link command and its saved-app behavior, then review the linked app-link documentation and the reported slack deploy selection flow. Confirm how team, environment, and app IDs are currently represented. Done means multiple apps can be retained and selected for later deployments without the current overwrite error.