Verify behavior when Azure deployment quota (800) is reached

## Summary

Aspire’s Azure deployment flow needs verification for the scenario where a subscription or resource group hits the Azure deployment quota limit (currently 800 deployments). We should confirm that Aspire surfaces a clear, actionable error when the quota is exceeded, and that any available automatic-deletion or cleanup behaviors are correctly triggered.

## Details

Azure limits ARM/Bicep deployments to 800 retained records per resource group. When this threshold is reached, new deployments fail until older records are manually removed or Azure automatically prunes them.

We need to validate how Aspire behaves in this situation:

* Does Aspire report the quota-exceeded error in a clear and discoverable way?
* Does Aspire’s deployment pipeline correctly detect and handle this failure, rather than surfacing opaque ARM errors?
* If automatic deployment record deletion is enabled on the target resource group, does Aspire allow that cleanup to occur and then retry successfully?
* If automatic deletion is not enabled, should Aspire detect the quota condition and surface guidance (or provide a follow-up action like `aspire do cleanup`)?

No files or tests are named. Start by locating Aspire’s Azure deployment flow and reproduce the condition where the subscription or resource group has 800 retained deployments. Verify the surfaced error, automatic cleanup and retry behavior, and the guidance shown when cleanup is unavailable.

Written by the indexing model from the issue text.