chore: Update to upstream release aptos-node-v1.13.3

[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 upstream/aptos-node-v1.13.3.

Steps to release an upgraded patched version:

• From dev, create a new branch aptos-node-v1.13.3-patched
• Pull the changes from upstream/aptos-node-v1.13.3 as follows:

- Apply the patched changes to this branch with the following:

git remote add upstream https://github.com/aptos-labs/aptos-core.git
git pull upstream refs/tags/aptos-node-v1.13.3 -r
git push origin aptos-node-v1.13.3-patched

- Then open a PR to `dev` with the changes, ensuring CI passes as usual
- Then, once this PR is merged, run the [release workflow](https://github.com/samuelburnham/aptos-core/actions/workflows/aptos-light-client-patch-release-pr.yml) and set the version input to `aptos-node-v1.13.3`. This will bump the version number in `PATCH_RELEASE.md` (since there is no Cargo version for the Aptos node) and open a PR from `release/aptos-node-v1.13.3-patched` to `dev`. The PR will run CI checks and provide an artifact for downstream companion PRs to test on. Note: This is a manual process as the rebase will likely create conflicts that must be resolved manually.
- When the PR is merged, it will automatically publish a GitHub release for `aptos-node-v1.13.3-patched` using the [merge workflow](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/9549401341

TODO: Move these instructions to separate patch-notes.md file and link to it here
TODO Do we need to explicitly tag the `-patched` branch or will the release job tag it with the  `softprops` workflow?