Fix azure pre-signed url for blob from different account

[nopcoder]

Fix #6595

[lynnro314]

LGTM. Thanks!

[arielshaqed]

Cool, thanks! I know very little about our Azure internals, @guy-har probably best look at that when he gets back. I am concerned that "adls" doesn't appear in this PR. So instead I'll just ask...

How was this tested?

[nopcoder]

Manual test and pending @lynnro314 test and verification for the specific data that the bug was found.

In order to reproduce you need to use azure and import data from different account.

The implementation have two implementation to handle (different API with Azure SDK):

1. The blob on the same account and you have access key configured.
2. The blob on another account which means you have service principle configured.

In the first one the API returns the URL after we provide the account/container.
In the second we request for credentials for the second account to get sign query parameters for our url and our code format the URL. The code used the object absolute path, and extracted the domain and use it for the signed URL.

This fix make sure we format the object location based azure default endpoint.

We should verify that the import works with the blob endpoint also for adls container and remove the support of import from this endpoint.
This code was added when import had to understand which algorithm to work based on the listing behaviour - which I don't think it is the case anymore (need to verify it).

So import with blob domain should work, and this fix should help existing data.

[nopcoder]

@lynnro314 ping or merge after verification on your environment.