azd down prompts init steps when running in a directory without a .azure file

[Austinauth]

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

Output from azd version
Run azd version and copy and paste the output here: azd version 0.8.0-beta.2 (commit 429b6cc)

Describe the bug
Running azd down in a directory with no .azure file prompts the user input an environment name, subscription and location before attempting to delete the resources from azure.

To Reproduce

Run azd down in a directory with no .azure file, but containing other template files.

Expected behavior
In this scenario we should probably show the user an error message in this scenario and not prompt them to enter the env, location, and sub. 

Additional context

• I ran azd down in a directory I had previously ran azd init in
• I did not complete the init originally, hence the reason there are some azd files in the directory, but not the .azure file
• I ran azd down in this directory because I wasn't sure if I had deployed to Azure and wanted to be safe and delete any resources if I had.

[spboyer]

Investigated. The root cause is in the DI registration (cmd/container.go:239-263) where *environment.Environment is wired through LoadOrInitInteractive() for all commands. When azure.yaml exists but no .azure directory/default env, azd down falls through to interactive env create/select prompts instead of erroring.

The fix would be to change the down command path to resolve the environment via envManager.Get() (non-interactive) instead of LoadOrInitInteractive(). If no environment exists, return a clear error:
'No environment is configured. Run azd env new or azd init first.'

This requires changing the DI wiring specifically for the down action to avoid the interactive fallback, which is a targeted but careful change in container.go.