$env:AZURE_ENV_NAME should be the seed for the ENV_NAME value used in the deployment, not used literally

[webstean]

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

Output from azd version
Run azd version and copy and paste the output here:
azd version 1.20.0 (commit 0031e30)

Describe the bug
#5189 resolved the uniqueness, when the location is interactively entered, but if the AZURE_LOCATION variable is set, AZD won't prompt for the location and use the value of AZURE_LOCATION, which recreates the same issue, two AZD deployment (azd up) will result in everything going into the same Azure Resource Group, creating problems when try to deleted.

To Reproduce
SET AZURE_LOCATION=xxx
cd azd1
azd up
cd ..\azd2
azd up
cd azd1
azd down - it will delete everything in azd1 and azd2 as well

Expected behavior
A clear and concise description of what you expected to happen.
The value of AZURE_LOCATION environment variable should be taken as a seed to generate a random unique value.

Environment
Information on your environment:
* Language name and version
* IDE and version : [e.g. Visual Studio 16.3]

Additional context
Add any other context about the problem here.
I want to set the AZURE_LOCATION variable to a unique name for each developer, so that is very obvious who created what resource. For example
AZURE_LOCATION = devtest_${USERNAME}
This works fine, until someone create 2 (or more) AZD environments.

[JeffreyCA]

The AZURE_LOCATION environment variable controls the Azure region where resources are deployed, and isn't intended as a way to uniquely identify resources.

I think AZURE_ENV_NAME might be what you're looking for?

azd env new <unique-env-name> can be used as well to create new environments across your projects

[webstean]

Sorry, @JeffreyCA I did mean AZURE_ENV_NAME, not AZURE_LOCATION. I open way too late one night.

[webstean]

I've corrected it, I really meant to say AZURE_ENV_NAME not AZURE_LOCATION