Allow app config validate to target config by client ID

[gonzaloriestra]

WHY are these changes introduced?

The interactivity audit found that app config validate could not combine --client-id and --config, which blocked validation of a specific config in fresh or stale-cache checkouts.

WHAT is this pull request doing?

• Allows app config validate to pair --client-id with --config.
• Adds command coverage and refreshes generated command docs.

How to test your changes?

• pnpm vitest run packages/app/src/cli/commands/app/config/validate.test.ts
• pnpm refresh-manifests

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]

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

• Add theme dev reconciliation strategy flag #7634
• Allow theme profile with Theme Access tokens #7633
• Add non-interactive app dev prompt bypasses #7632
• Allow app config validate to target config by client ID #7631 👈 (View in Graphite)
• Allow app config link to target config by client ID #7630
• main

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