chore: Update to upstream release `aptos-node-v1.15.2`

[samuelburnham]

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

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

Steps to release an upgraded patched version:

• Rebase dev onto the changes from upstream/aptos-node-v1.15.2 as follows:

git remote add upstream https://github.com/aptos-labs/aptos-core.git
git reset --hard refs/tags/aptos-node-v1.15.2
# TODO: Merge into one commit for simplicity
git cherry-pick 7c9a8bcd79376cf1479a3432b48127a56945cabb
git cherry-pick d14dc0c286e704883ca453a40ab4531702c86f71
git cherry-pick 15f91a32989ea63224064862167136b17baf1128
git cherry-pick <CI-commits>
git push origin dev -f

• Then, run the release workflow and set the version input to aptos-node-v1.15.2. 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.15.2-patched to dev. The PR will run CI checks 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.15.2-patched using the merge workflow.

This issue was created by the workflow at https://github.com/lurk-lab/aptos-core/actions/runs/9966015938

TODO: Move these instructions to separate patch-notes.md file and link to it here