[Aspire extension] Phase 4: Map complete azd workflows to Aspire

Parent epic: #9479

Depends on the initial `microsoft.azd.aspire` provider implementation.

## Objective

Support the complete set of azd workflows expected by Aspire customers while using Aspire CLI operations underneath.

## Required workflow mapping

- `azd init`: discover/select the AppHost and generate `host: aspire`.
- `azd package`: execute the appropriate Aspire publish/package steps.
- `azd provision`: provision infrastructure without unnecessarily redeploying application code.
- `azd deploy`: deploy compute without unnecessarily reprovisioning completed infrastructure.
- `azd up`: compose package, provision, and deploy through azd orchestration.
- `azd down`: perform state-aware destruction without interactive Aspire prompts.
- `azd infra generate`: export generated infrastructure artifacts.
- `azd env refresh`: query persisted deployment state and return outputs.
- `azd pipeline config`: install and invoke compatible extension/Aspire CLI versions in CI.
- Project and service hooks, `--no-prompt`, output formats, cancellation, and timeouts.

## Design considerations

- Identify which operations are directly supported by Aspire CLI pipeline steps.
- Coordinate missing separation or state contracts with the Aspire team rather than relying on private protocols.
- Preserve azd environment ownership and deterministic CI behavior.
- Ensure aggregate Aspire artifacts still produce useful azd endpoint and deployment output.

## Exit criteria

- Each listed command has a documented and tested behavior.
- App Service and Container Apps scenarios work based on AppHost configuration.
- Repeated and partial workflows do not duplicate or corrupt deployment state.