[eastl] update to 3.27.01

[alandtse]

• Changes comply with the maintainer guide.
• SHA512s are updated for each updated download.
• The "supports" clause reflects platforms that may be fixed by this new version.
• Any fixed CI baseline entries are removed from that file.
• Any patches that are no longer applied are deleted from the port's directory.
• The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
• Only one version is added to each modified port's versions file.

[Copilot]

Pull request overview

This PR updates the EASTL (Electronic Arts Standard Template Library) from version 3.21.23 to 3.27.01, along with its dependency EABase to version dated 2025-08-03.

• EASTL library updated to version 3.27.01 with corresponding SHA512 hash update
• EABase dependency updated to version-date 2025-08-03 with new REF and SHA512 hash
• Version database files updated to reflect the new versions in the baseline

Reviewed changes

Copilot reviewed 8 out of 8 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
versions/e-/eastl.json	Adds new version entry for EASTL 3.27.01 with git-tree hash
versions/e-/eabase.json	Adds new version entry for EABase dated 2025-08-03 with git-tree hash
versions/baseline.json	Updates baseline versions for both eabase and eastl packages
ports/eastl/vcpkg.json	Changes version field from "version" to "version-string" format and updates to 3.27.01
ports/eastl/portfile.cmake	Updates SHA512 hash for the new EASTL version source archive
ports/eastl/0001-fix-cmake-install.patch	Updates the GIT_TAG reference in the patch to match new EABase commit
ports/eabase/vcpkg.json	Updates version-date to 2025-08-03
ports/eabase/portfile.cmake	Updates REF to new commit and SHA512 hash for the new EABase version

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[vicroms]

Please use version instead of version-string.

[vicroms]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).