chore: defer queued changesets until after security release

[josephfusco]

Summary

Removes three queued changesets from canary so the next Version Packages PR is scoped to the security fix only. The changeset files remain recoverable from git history and will be reintroduced after the security release ships.

Deferred

• blockset-cleanup-on-failed-extraction.md
• handle-generate-home-url.md
• hash-equals-secret-comparison.md

Reintroducing post-release

git checkout 0598216c -- .changeset/blockset-cleanup-on-failed-extraction.md \
                         .changeset/handle-generate-home-url.md \
                         .changeset/hash-equals-secret-comparison.md

Test plan

• After merge, confirm the open Version Packages PR (Version Packages #2361) is updated to reflect no pending changesets.
• After the security changeset lands, confirm the regenerated Version Packages PR contains only that changeset.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 8eda169

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[github-actions]

📦 Next.js Bundle Analysis for @faustwp/getting-started-example

This analysis was generated by the Next.js Bundle Analysis action. 🤖

This PR introduced no changes to the JavaScript bundle! 🙌