Harden Azure AI agent scenario resource setup #10202

• Make sure you've installed the latest version using instructions

N/A - this issue concerns repository scenario-test infrastructure.

Output from azd version
Run azd version and copy and paste the output here:

N/A

Describe the bug
The azure.ai.agents interactive scenario suite can construct Foundry project names longer than the 32-character service limit. Deploy-verification scenarios can also retain a model SKU from an adopted manifest that is unavailable in the selected region, causing setup to fail before the intended behavior is exercised.

To Reproduce

1. Configure the scenario profile with a multi-character prefix such as your-alias.
2. Run a Tier 1 init scenario using its run-scoped instance identifier, or run Tier 2 setup with the full run ID.
3. Observe that the composed Foundry project name can exceed 32 characters.
4. Run a Tier 1b deploy verifier against a scaffold whose adopted model SKU is unavailable in the selected region.

Expected behavior
Scenario orchestration derives a deterministic Foundry project name no longer than 32 characters while preserving the complete run-unique suffix. Tier 1b and Tier 2 setup optionally replace and verify the scaffold's managed deployment model and SKU before provisioning.

Environment
Information on your environment:

• Scenario suite: cli/azd/extensions/azure.ai.agents/tests/cli-interactive-tester-scenarios
• Host: Windows/WSL and native Linux/macOS scenario runners

Additional context
Tracked by #10190.