chore: Upstream release

[samuelburnham]

A new Aptos PFN release: aptos-node-v1.13.3 is available at https://github.com/aptos-labs/aptos-core/releases/tag/aptos-node-v1.13.3.

A new branch associated with these changes was pushed locally at aptos-node-v1.13.3.

Steps to release an upgraded patched version:

• Checkout a copy of aptos-node-v1.13.3 as release/aptos-node-v1.13.3-patched to prepare for release
• Apply the patched changes to this branch with e.g. git rebase --onto or git cherry-pick. This is a manual process as it often creates conflicts. TODO document the full command, and do we need to explicitly tag the -patched branch or will the release job tag it with the softprops workflow?
• Then, run the release workflow at https://github.com/samuelburnham/aptos-core/actions/workflows/aptos-light-client-patch-release-pr.yml. This will bump the version number in README.md (since there is no Cargo version for the Aptos node) and open a PR to release/aptos-node-v1.13.3-patched for the release. The PR will run CI checks, solicit review, and provide an artifact for downstream companion PRs to test on.
• When the PR is merged, it will automatically publish a GitHub release for aptos-node-v1.13.3-patched using https://github.com/samuelburnham/aptos-core/actions/workflows/aptos-light-client-patch-release-publish.yml.

This issue was created by the workflow at https://github.com/samuelburnham/aptos-core/actions/runs/9547916283