chore(codegen): bump smithy-typescript commit

[syall]

Issue

Issue number, if available, prefixed with "#"

N/A.

Description

What does this implement/fix? Explain your changes.

Bump smithy-typescript commit.

Dependent on: #5232

Testing

How was this change tested?

1. yarn generate-clients
2. node scripts/runtime-dependency-version-check/runtime-dep-version-check.js
3. yarn

The @smithy package dependencies were updated, e.g. in client-accessanalyzer:

diff --git a/clients/client-accessanalyzer/package.json b/clients/client-accessanalyzer/package.json
index 4933b35017c..8ad3252c72b 100644
--- a/clients/client-accessanalyzer/package.json
+++ b/clients/client-accessanalyzer/package.json
@@ -33,27 +33,27 @@
     "@aws-sdk/util-endpoints": "*",
     "@aws-sdk/util-user-agent-browser": "*",
     "@aws-sdk/util-user-agent-node": "*",
-    "@smithy/config-resolver": "^2.0.8",
-    "@smithy/fetch-http-handler": "^2.1.3",
-    "@smithy/hash-node": "^2.0.7",
-    "@smithy/invalid-dependency": "^2.0.7",
-    "@smithy/middleware-content-length": "^2.0.9",
-    "@smithy/middleware-endpoint": "^2.0.7",
-    "@smithy/middleware-retry": "^2.0.10",
-    "@smithy/middleware-serde": "^2.0.7",
-    "@smithy/middleware-stack": "^2.0.0",
-    "@smithy/node-config-provider": "^2.0.10",
-    "@smithy/node-http-handler": "^2.1.3",
-    "@smithy/protocol-http": "^3.0.3",
-    "@smithy/smithy-client": "^2.1.4",
-    "@smithy/types": "^2.3.1",
-    "@smithy/url-parser": "^2.0.7",
+    "@smithy/config-resolver": "^2.0.10",
+    "@smithy/fetch-http-handler": "^2.1.5",
+    "@smithy/hash-node": "^2.0.9",
+    "@smithy/invalid-dependency": "^2.0.9",
+    "@smithy/middleware-content-length": "^2.0.11",
+    "@smithy/middleware-endpoint": "^2.0.9",
+    "@smithy/middleware-retry": "^2.0.12",
+    "@smithy/middleware-serde": "^2.0.9",
+    "@smithy/middleware-stack": "^2.0.2",
+    "@smithy/node-config-provider": "^2.0.12",
+    "@smithy/node-http-handler": "^2.1.5",
+    "@smithy/protocol-http": "^3.0.5",
+    "@smithy/smithy-client": "^2.1.6",
+    "@smithy/types": "^2.3.3",
+    "@smithy/url-parser": "^2.0.9",
     "@smithy/util-base64": "^2.0.0",
     "@smithy/util-body-length-browser": "^2.0.0",
     "@smithy/util-body-length-node": "^2.1.0",
-    "@smithy/util-defaults-mode-browser": "^2.0.8",
-    "@smithy/util-defaults-mode-node": "^2.0.10",
-    "@smithy/util-retry": "^2.0.0",
+    "@smithy/util-defaults-mode-browser": "^2.0.10",
+    "@smithy/util-defaults-mode-node": "^2.0.12",
+    "@smithy/util-retry": "^2.0.2",
     "@smithy/util-utf8": "^2.0.0",
     "tslib": "^2.5.0",
     "uuid": "^8.3.2"

The codegen diff also includes adding service and operation to the smithy context for each command, e.g. for the command ApplyArchiveRuleCommand in client-accessanalyzer:

diff --git a/clients/client-accessanalyzer/src/commands/ApplyArchiveRuleCommand.ts b/clients/client-accessanalyzer/src/commands/ApplyArchiveRuleCommand.ts
index 6a4a2ce1522..79c990da595 100644
--- a/clients/client-accessanalyzer/src/commands/ApplyArchiveRuleCommand.ts
+++ b/clients/client-accessanalyzer/src/commands/ApplyArchiveRuleCommand.ts
@@ -11,6 +11,7 @@ import {
   MetadataBearer as __MetadataBearer,
   MiddlewareStack,
   SerdeContext as __SerdeContext,
+  SMITHY_CONTEXT_KEY,
 } from "@smithy/types";
 
 import { AccessAnalyzerClientResolvedConfig, ServiceInputTypes, ServiceOutputTypes } from "../AccessAnalyzerClient";
@@ -130,6 +131,10 @@ export class ApplyArchiveRuleCommand extends $Command<
       commandName,
       inputFilterSensitiveLog: (_: any) => _,
       outputFilterSensitiveLog: (_: any) => _,
+      [SMITHY_CONTEXT_KEY]: {
+        service: "AccessAnalyzer",
+        operation: "ApplyArchiveRule",
+      },
     };
     const { requestHandler } = configuration;
     return stack.resolve(

Additional context

Add any other context about the PR here.

N/A.

---

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[github-actions]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and link to relevant comments in this thread.