[maven]: Bump software.amazon.awssdk:bom from 2.49.3 to 2.50.1

[dependabot]

Bumps software.amazon.awssdk:bom from 2.49.3 to 2.50.1.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[github-actions]

Claude AI review

No findings.

This PR contains a single change: the aws.sdk.version property in pom.xml is bumped from 2.49.3 to 2.50.1 (pom.xml:55). The property is consumed by the AWS SDK BOM <dependencyManagement> import (pom.xml:70), so the version reference stays consistent and no other code changes are involved. This is a routine patch-level minor bump within the 2.x line, so there is no expected impact on public API, generic typing, serialization, checkpoint/replay semantics, or the execution lifecycle.

Residual test risk: The diff itself adds no tests, which is appropriate for a dependency bump. The real risk is behavioral drift in the underlying AWS SDK (2.49.3 → 2.50.1) — the diff cannot reveal whether any transitive SDK behavior (e.g., serialization defaults, retry/timeout defaults, or DynamoDB/Lambda client behavior used by the durable execution runtime) changed. That risk is entirely covered by the project's existing build and integration/conformance test suite passing against the new version, which should be confirmed green in CI before merge.

Reviewed commit df52bf8e9c81311fa3ccf202cffa77b33a7f99d5. Workflow run

[github-actions]

Codex AI review

No actionable findings.

Residual risk: the dependency update was not built or tested because the review was restricted to read-only inspection.

Reviewed commit df52bf8e9c81311fa3ccf202cffa77b33a7f99d5. Workflow run