BlockBlobClient.SyncUploadFromUriAsync produces 0 byte file

### Which service(blob, file, queue, table) does this issue concern?
blob

### Which version of the Azurite was used?
3.13.1

### Where do you get Azurite? (npm, DockerHub, NuGet, Visual Studio Code Extension)
npm

### What's the Node.js version?
14.15.0

### What problem was encountered?
0 byte file produced when using Azure.Storage.Blobs, BlockBlobClient.SyncUploadFromUriAsync

### Steps to reproduce the issue?

`npm install azurite@3.13.1`

NuGet packages

```xml



```

simplified code snippet

```C#
using Azure.Storage.Blobs;
using Azure.Storage.Blobs.Specialized;
...
var blobServiceClient = new BlobServiceClient("UseDevelopmentStorage=true");
var containerClient = blobServiceClient.GetBlobContainerClient("transfertothis");
await containerClient.CreateIfNotExistsAsync().ConfigureAwait(false);
var blobClient = containerClient.GetBlockBlobClient("1.0.0.0.zip");
await blobClient.SyncUploadFromUriAsync(new Uri("http://127.0.0.1:10000/devstoreaccount1/dev/1.0.0.0.zip"), false).ConfigureAwait(false);
```
start azurite and add a file in container dev called 1.0.0.0.zip. Set dev container permissions to `public read blob`.

run code and observe that transfertothis/1.0.0.0.zip is created within it but is 0bytes!

If possible, please provide the debug log using the -d parameter, replacing \ with an appropriate path for your OS, or review the instructions for docker containers:

Microsoft employee please reach out to me on teams for logs or screenshare if needed.

```
-d ""
```

Please be sure to remove any PII or sensitive information before sharing!
The debug log will log raw request headers and bodies, so that we can replay these against Azurite using REST and create tests to validate resolution.

### Have you found a mitigation/solution?
no