Getting UnsupportedHeader code while trying to upload artifact

Describe the bug
Getting UnsupportedHeader code while trying to upload artifact

To Reproduce
Steps to reproduce the behavior:

1. We noticed UnsupportedHeader error coming in x-ms-error-code in version 2.1.8 @action/artifact

2. We upgraded @actions/artifact to 2.2.0 in our package.json

3. We have made call to uploadArtifact(artifactName, files, root directory, {retentionDays} of DefaultArtifactClient of @actions/artifact from our js file.

4. We observed below behaviour:
   upload-artifact.js makes call to uploadZipToBlobStorage under blob-upload.js where it makes a call to uploadStream method present in storage-blob and error occurs at uploadStream method where error says : RestError: One of the HTTP headers specified in the request is not supported.

5. When we look at the request header it is as below :
   

Expected behavior
Requested Artifact Should get uploaded to workflow .

Screenshots
Attached request header in point 5 above.

Response header looks like below :

Additional context
My first guess would be if x-ms-version 2025-01-05 is able to support the header being passed from @action/artifact ?

Start by reproducing the failure with @actions/artifact 2.2.0 and trace upload-artifact.js through blob-upload.js to storage-blob's uploadStream method. Inspect the request headers and the x-ms-error-code response, especially the reported x-ms-version 2025-01-05. Done means the artifact uploads successfully without the UnsupportedHeader error.