encountering 403 when trying to update the properties

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

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

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

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

### What problem was encountered?
We are using the Azurite for testing our application.
We have a spark application that uses AzureNativeFileSystem (part of azure hadoop 2.7.3 package, Maven Repository: https://mvnrepository.com/artifact/org.apache.hadoop/hadoop-azure/2.7.3)
With the help of the above library, mkdir calls are successful when using the azurite emulator.
However, when it tries to delete or create an object, we get the 403 exceptions.
We are using the same devstoreaccount1 account credentials for all operations.
We can see that the 403 errors are encountered when the above library tries to update the last modification time (or properties) for the parent folder where it tries to create an object

In the below, we can see that the HEAD succeeds while PUT on the properties return the 403.

127.0.0.1 - - [10/Feb/2022:08:51:34 +0000] "HEAD /devstoreaccount1/sparkconnectortests/dummyaccount/AgAAAA==/AgAAAIUFBKE=.Cosmos/PartitionId=ff11b509-7bd9-4234-aeac-4f5f4e134c85 HTTP/1.1" 200 0
**127.0.0.1 - - [10/Feb/2022:08:51:34 +0000] "HEAD /devstoreaccount1/sparkconnectortests/dummyaccount/AgAAAA==/AgAAAIUFBKE=.Cosmos/PartitionId=ff11b509-7bd9-4234-aeac-4f5f4e134c85 HTTP/1.1" 200 0
127.0.0.1 - - [10/Feb/2022:08:51:34 +0000] "PUT /devstoreaccount1/sparkconnectortests/dummyaccount/AgAAAA==/AgAAAIUFBKE=.Cosmos/PartitionId=ff11b509-7bd9-4234-aeac-4f5f4e134c85?comp=properties HTTP/1.1" 403 -**

### Steps to reproduce the issue?

Using hadoop-azure 2.7.3
Debug logs are attached.
[debug.log](https://github.com/Azure/Azurite/files/8039574/debug.log)

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:

```
-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?
Using Azurite 2.7

### Other information:
Without any changes in our code, we can continue the test cases by using Azurite 2.7 or now deprecated Azure Storage Emulator suggesting the problem is specific to Azurite 3.x
The creates with az cli works fine.