provide container not found error directly in blobfuse mount error when --container-name does not exist

[andyzhangx]

Currently when we mount a non-existing container, it would report error "failed to authenticate credentials for azstorage", which is not quite clear error, unless I have opened the /var/log/blobfuse2.log, and then I found it's container not found error, it's better to provide container not found error directly in blobfuse mount error when --container-name does not exist, that would save customers lots of debugging time when we hit such scenario in AKS.

blobfuse2 test --container-name=cdpblobnonprodeus --tmp-path=/tmp/blobfuse -o allow_other --file-cache-timeout-in-seconds=120
*** blobfuse2: A new version [2.4.1] is available. Consider upgrading to latest version for bug-fixes & new features. ***
Error: failed to initialize new pipeline [failed to authenticate credentials for azstorage]

[syeleti-msft]

Sure, that make sense

[andyzhangx]

@syeleti-msft thanks for the check, failed to authenticate credentials for azstorage error does not provide enough info, besides container not exist error, could blobfuse return error provide more meaningful error for other errors if possible, thanks.

[syeleti-msft]

Sure, I tried to return the error code that come from the SDK when failure happens.
PR: #1648