chore: bump arsenal to ARSN-572 PoC branch for e2e trace context testing

Temporarily point the arsenal dep at scality/Arsenal#improvement/ARSN-572/trace-context
(commit 01693cde) so we can validate end-to-end trace context propagation
from cloudserver HTTP spans through to the MongoDB oplog on a test
cluster. ARSN-572 adds traceContext plumbing on metadata writes; cloudserver
needs no code change thanks to OTEL async context hooks.

Revert to a clean #8.3.x release tag before this PR merges, once ARSN-572
ships.

Issue: CLDSRV-884

Author: delthas

package.json

@@ -36,7 +36,7 @@
     "@opentelemetry/sdk-node": "^0.55.0",
     "@opentelemetry/sdk-trace-base": "^1.28.0",
     "@smithy/node-http-handler": "^3.0.0",
-    "arsenal": "git+https://github.com/scality/Arsenal#8.3.9",
+    "arsenal": "git+https://github.com/scality/Arsenal#improvement/ARSN-572/trace-context",
     "async": "2.6.4",
     "bucketclient": "scality/bucketclient#8.2.7",
     "bufferutil": "^4.0.8",

yarn.lock

@@ -7287,9 +7287,9 @@ arraybuffer.prototype.slice@^1.0.4:
   optionalDependencies:
     ioctl "^2.0.2"
 
-"arsenal@git+https://github.com/scality/Arsenal#8.3.9":
-  version "8.3.9"
-  resolved "git+https://github.com/scality/Arsenal#51e5b761f7f0612a722c828fa3d43b438c50ab7c"
+"arsenal@git+https://github.com/scality/Arsenal#improvement/ARSN-572/trace-context":
+  version "8.3.10"
+  resolved "git+https://github.com/scality/Arsenal#ca456c949305b5f2fcd3a25e55b371dd02a24aeb"
   dependencies:
     "@aws-sdk/client-kms" "^3.975.0"
     "@aws-sdk/client-s3" "^3.975.0"
@@ -7298,6 +7298,7 @@ arraybuffer.prototype.slice@^1.0.4:
     "@azure/identity" "^4.13.0"
     "@azure/storage-blob" "^12.31.0"
     "@js-sdsl/ordered-set" "^4.4.2"
+    "@opentelemetry/api" "^1.9.0"
     "@scality/hdclient" "^1.3.1"
     "@smithy/node-http-handler" "^4.3.0"
     "@smithy/protocol-http" "^5.3.5"