Use -Mail for test resources local user lookup to support TME

[benbp]

For TME accounts, the -UserPrincipalName does not match the email (e.g. [email protected]) and is instead like foobar_microsoft.com#EXT#@<tenant>), so the local user id/oid lookup is broken for TME testing. Using -Mail works as the value is the same across tenants.

So for local TME testing, one can do:

Set-AzContext -Subscription '<tme subscription>' -Tenant '<tme tenant>'

./eng/common/TestResources/New-TestResources.ps1 -ServiceDirectory <dir> -SubscriptionId '<tme subscription>'

At a certain point we will switch the default off playground and the -Subscription override won't be necessary, but we'll have to add more UX handling to help people make sure they are on the right az context.

CC @catalinaperalta

[azure-sdk]

The following pipelines have been queued for testing:
java - template
java - template - tests
js - template
net - template
net - template - tests
python - template
python - template - tests
You can sign off on the approval gate to test the release stage of each pipeline.
See eng/common workflow

[azure-sdk]

The following pipelines have been queued for testing:
java - template
java - template - tests
js - template
net - template
net - template - tests
python - template
python - template - tests
You can sign off on the approval gate to test the release stage of each pipeline.
See eng/common workflow

[azure-sdk]

The following pipelines have been queued for testing:
java - template
java - template - tests
js - template
net - template
net - template - tests
python - template
python - template - tests
You can sign off on the approval gate to test the release stage of each pipeline.
See eng/common workflow