Fix the inconsistent behavior between Spine vector's setSize and std::vector's resize, which causes the Spine vector to allocate additional space upfront.

[bofeng-song]

Re: #
EsotericSoftware/spine-runtimes#2830

As shown in the screenshot, when the vector is empty, the first call to resize results in capacity and size being equal, meaning no additional capacity is allocated.

Changelog

---

Continuous Integration

This pull request:

• needs automatic test cases check.

  Manual trigger with @cocos-robot run test cases afterward.

• does not change any runtime related code or build configuration

  If any reviewer thinks the CI checks are needed, please uncheck this option, then close and reopen the issue.

---

Compatibility Check

This pull request:

• changes public API, and have ensured backward compatibility with deprecated features.
• affects platform compatibility, e.g. system version, browser version, platform sdk version, platform toolchain, language version, hardware compatibility etc.
• affects file structure of the build package or build configuration which requires user project upgrade.
• introduces breaking changes, please list all changes, affected features and the scope of violation.

[bofeng-song]

I've sent a PR to Spine

[github-actions]

Code Size Check Report

Wechat (WASM)	Before	After	Diff
2D Empty (legacy pipeline)	1005779 bytes	1005779 bytes	✅ 0 bytes
2D All (legacy pipeline)	2669443 bytes	2669527 bytes	⚠️ +84 bytes
2D All (new pipeline)	2757950 bytes	2758034 bytes	⚠️ +84 bytes
(2D + 3D) All	10013834 bytes	10013918 bytes	⚠️ +84 bytes

Web (WASM + ASMJS)	Before	After	Diff
(2D + 3D) All	16921864 bytes	16829288 bytes	👍 -92576 bytes

Interface Check Report

This pull request does not change any public interfaces !