BlobTrigger with BlockBlobClient with managed identity connection string returns wrong URI in China

### Description

I have a function like this:
```c#
[Function("Foo")]
public async Task Run(
[BlobTrigger("foo", Connection = "Foo")]
BlockBlobClient blobClient,
Uri uri
)
```

the connection is defined using the [managed identity syntax](https://learn.microsoft.com/en-us/azure/azure-functions/functions-reference?tabs=blob&pivots=programming-language-csharp#connecting-to-host-storage-with-an-identity), ie
```
"Foo__blobServiceUri": "https://foo.blob.core.chinacloudapi.cn"
```

In China, `blobClient` has a URI of `https://foo.blob.core.windows.net` - it should be `https://foo.blob.core.chinacloudapi.cn`.

I also added the `Uri` binding because that has the correct URI, so I can create my own `BlockBlobClient` from `uri` as a workaround.

### Steps to reproduce

As described above

Start by reproducing the BlobTrigger with a BlockBlobClient and the managed identity setting Foo__blobServiceUri in the issue. Compare the injected BlockBlobClient URI with the Uri binding in the China cloud environment; done means the client URI uses the configured chinacloudapi.cn endpoint rather than windows.net.

Written by the indexing model from the issue text.