Use client IDs for app management and dev requests

[dmerand]

WHY are these changes introduced?

CLI configuration identifies apps by client ID. Use that same identifier to select apps in App Management and App Dev requests, rather than passing database IDs.

WHAT is this pull request doing?

Use clientId for Management/Dev mutations and scope version-tag lookup to the selected app. Use existing appByKey queries for nested version and install-count data. Keep public IDs, dashboard links, metadata/access checks, and signed-upload cache partitions unchanged.

This does not remove the app lookups that supply metadata or access context. No reduction in network requests is claimed.

Keep this PR in draft until the server accepts the new arguments and resolves organization context from clientId. Local generation uses the candidate server schema; the World-main schema check and deployed compatibility still need verification.

Use the PR snapshot in a disposable development app/store for the manual commands below, after compatible server deployment. --no-release creates a version; it is not a dry run.

How to manually test your changes?

shopify app versions list --json
shopify app deploy --no-release
shopify app dev
shopify app dev clean

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 — I've identified the correct bump type (patch for bug fixes · minor for new features · major for breaking changes) and added a changeset with pnpm changeset add