feat: add Foundry project infrastructure

[Hui Miao (huimiu)]

Why this is needed

Foundry infrastructure ejection must coexist with existing user infrastructure. Without explicit planning, a project can overwrite paths, lose provider information, or leave a partial ejection behind.

Approach

Add Projects-side infrastructure planning and installation for Bicep and Terraform. The implementation validates paths, providers, modules, layers, and collisions before staging changes, then updates project configuration atomically with rollback support.

Scope

This draft contains only the Projects infrastructure and hardening changes. Agents delegation and recording-proxy changes are separate drafts.

Dependency

This draft is based on #9559. After that PR is merged and its base branch is deleted, GitHub can retarget this PR to main.

[azure-pipelines]

Azure Pipelines:
Successfully started running 1 pipeline(s).
20 pipeline(s) were filtered out due to trigger conditions.
There may be pipelines that require an authorized user to comment /azp run to run.

[microsoft-github-policy-service]

Hi @Hui Miao (@huimiu). Thank you for your interest in helping to improve the Azure Developer CLI experience and for your contribution. We've noticed that there hasn't been recent engagement on this pull request. If this is still an active work stream, please let us know by pushing some changes or leaving a comment. Otherwise, we'll close this out in 7 days.

[microsoft-github-policy-service]

Hi @Hui Miao (@huimiu). Thank you for your contribution. Since there hasn't been recent engagement, we're going to close this out. Feel free to respond with a comment containing "/reopen" if you'd like to continue working on these changes. Please be sure to use the command to reopen or remove the "no-recent-activity" label; otherwise, this is likely to be closed again with the next cleanup pass.