Block Library: Restore 3.2.22 release metadata

[ciampo]

Related: #81295

What?

Updates @wordpress/block-library metadata on wp/5.8 to match version 3.2.22, which is already published to npm.

It also moves the Legacy Widget removal entry from Unreleased into 3.2.5, the first published package version that contained the change.

Why?

The manual package publication did not update this branch's package manifest or changelog. The Legacy Widget entry was also still marked as unreleased even though it had shipped in 3.2.5.

How?

Bumps packages/block-library/package.json, adds the 3.2.22 release entry for the Post Date output fix, and records the older Legacy Widget change under 3.2.5. This PR does not publish the package again.

Testing Instructions

1. Confirm packages/block-library/package.json reports version 3.2.22.
2. Confirm packages/block-library/CHANGELOG.md contains the 3.2.22 (2026-08-06) release with the Post Date entry.
3. Confirm the Legacy Widget entry is under 3.2.5 (2021-06-14) and Unreleased is empty.
4. Confirm the diff contains only those two metadata files.

Use of AI Tools

Codex was used to prepare and verify these metadata-only changes and this pull request.

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: ciampo <mciampini@git.wordpress.org>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.