Add flags to avoid prompts in app config link

[gonzaloriestra]

WHY are these changes introduced?

Related to https://github.com/shop/issues-develop/issues/22869

The interactivity audit found that shopify app config link --client-id <id> can still prompt for a local configuration file name when the target file cannot be inferred.

WHAT is this pull request doing?

• Adds --file-name to choose the config file that app config link should create.
• Adds --force to overwrite an existing config file without prompting.

How to test your changes?

With a new client-id (not used in any toml file) and an existing shopify.app.toml:

• shopify app config link --client-id => should ask for the file
• shopify app config link --client-id --file-name staging => should create shopify.app.staging.toml
• shopify app config link --client-id --file-name shopify.app.toml => already exists error
• shopify app config link --client-id --file-name shopify.app.toml --force => works

Checklist

• I've considered possible cross-platform impacts (Mac, Linux, Windows)
• I've considered possible documentation changes
• I've considered analytics changes to measure impact
• The change is user-facing, so I've added a changelog entry with pnpm changeset add

[gonzaloriestra]

• Add non-interactive app dev prompt bypasses #7632 : 2 dependent PRs (#7633 , #7634 )
• Allow app config validate to target config by client ID #7631
• Add flags to avoid prompts in app config link #7630 👈 (View in Graphite)
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[isaacroldan]

link already accepts a config flag, how does that affect --file-name/--force?

[gonzaloriestra]

--config and --filename are exclusive flags, so you can't use them together