fix: restore next peer dependency ranges narrowed by dependabot

[josephfusco]

Related: #2495

Neither range has been released yet, so merging this before Version Packages (#2530) keeps the next release from dropping Next.js 12–16.2 support; #2495 was a grouped "ancestor dependency" bump, which rewrote the peer ranges despite versioning-strategy: increase-if-necessary, so similar Dependabot PRs touching next need a look at peerDependencies.

Use of AI Tools

AI assistance: Yes
Tool(s): Claude Code
Model(s): Claude Opus 5.5
Used for: Assisting with spotting the narrowed ranges during issue triage and restoring them.

[changeset-bot]

🦋 Changeset detected

Latest commit: 56c808e

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 2 packages

Name	Type
@faustwp/core	Patch
@faustwp/blocks	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another 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. 🤖

⚠️ Global Bundle Size Increased

Page	Size (compressed)
global	247.07 KB (🟡 +12 B)

Details

The global bundle is the javascript bundle that loads alongside every page. It is in its own category because its impact is much higher - an increase to its size means that every page on your website loads slower, and a decrease means every page loads faster.

Any third party scripts you have added directly to your app using the <script> tag are not accounted for in this analysis

If you want further insight into what is behind the changes, give @next/bundle-analyzer a try!