Allow theme profile with Theme Access tokens

[gonzaloriestra]

WHY are these changes introduced?

The interactivity audit found that theme profile required browser OAuth even when a Theme Access token was available for non-interactive runs.

WHAT is this pull request doing?

• Allows theme profile to use Theme Access tokens.
• Keeps the existing rejection for raw Admin API tokens with clearer guidance.

How to test your changes?

• pnpm vitest run packages/theme/src/cli/services/profile.test.ts

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 👈 (View in Graphite)
• Add non-interactive app dev prompt bypasses #7632
• Allow app config validate to target config by client ID #7631
• 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.