[Feature request] Allow --testing-account to work alongside --profile

[luxferre]

Issue: Cannot separate upload account from testing account when using config profiles

Setup:

• Platform version 2025.2+
• Using config profiles with variables in TypeScript code
• Project deployed to Account 1 (full-featured dev account)
• Need to test/install app locally on Account 2

Problem:
When running hs project dev, I need to:

• Upload project to Account 1 (using config profile for variables)
• Install and test the app on Account 2

The CLI has --testing-account and --project-account flags, but they are mutually exclusive with --profile:

hs project dev --profile profile1 --testing-account → Error: "Arguments profile and testing-account are mutually exclusive"
Since I need config profile variables in my code, I cannot use --testing-account without --profile.

Current workarounds are insufficient:

• Creating a second profile for Account 2 causes the project to deploy to Account 2, which is unwanted
• Manual installation via UI doesn't solve the local dev flow

Feature request:
Allow --testing-account to work alongside --profile, so the profile handles variables and upload account, while --testing-account specifies where to install for local development.

[joe-yeager]

Thanks for the feature request submission @luxferre - I will take this back to the team for discussion.