Improve error message when no credentials are set for DefaultAzureCredential

[vcolin7]

As reported by @JonathanGiles:

When I run an app on my Mac that has not got any credentials set up that DefaultAzureCredential can use, it is bad form to have a very long and scary exception message about PowerShell not being found when I am running on a MacBook – can we please make this error message nicer?

What I would like to see is way more context about how I am supposed to resolve this. Give links out to aka.ms links that explain to me what env vars I need to set, etc. The problem with this error message is that it tells me the problem without telling me enough on how to fix it.

We need to wrap and handle this more appropriately, as it pretty much kills the ability to graalvm native-image applications, as the IOException thrown on line 72 in the link below pretty much causes everything to come to a screaming halt.

Because we are trying to be helpful to users with the DAC, we need to be careful that if the environment is not what we expect that we don’t cause more trouble than benefit.

The error in question:

EnvironmentCredential authentication unavailable. Environment variables are not fully configured.
ManagedIdentityCredential authentication unavailable. Connection to IMDS endpoint cannot be established, Connect timed out.
SharedTokenCacheCredential authentication unavailable. No accounts were found in the cache.
IntelliJ Authentication not available. Please log in with Azure Tools for IntelliJ plugin in the IDE.
Failed to read Vs Code credentials from Mac Native Key Chain.
AzureCliCredential authentication unavailable. Please run 'az login' to set up account
Unable to execute PowerShell. Please make sure that it is installed in your system
    at com.azure.identity.ChainedTokenCredential.lambda$getToken$3 (ChainedTokenCredential.java:77)
...
Caused by: java.io.IOException: Cannot run program "pwsh": error=2, No such file or directory
    at java.lang.ProcessBuilder.start (ProcessBuilder.java:1128)
    at java.lang.ProcessBuilder.start (ProcessBuilder.java:1071)
    at com.azure.identity.implementation.PowershellManager.lambda$initSession$0 (PowershellManager.java:62)
...
Caused by: java.io.IOException: error=2, No such file or directory
    at java.lang.ProcessImpl.forkAndExec (Native Method)
    at java.lang.ProcessImpl.<init> (ProcessImpl.java:319)
    at java.lang.ProcessImpl.start (ProcessImpl.java:250)
    at java.lang.ProcessBuilder.start (ProcessBuilder.java:1107)
    at java.lang.ProcessBuilder.start (ProcessBuilder.java:1071)
    at com.azure.identity.implementation.PowershellManager.lambda$initSession$0 (PowershellManager.java:62)
...

[g2vinay]

Resolved via #24512