chore(deps): drop @wordpress dependencies to wp-7.0 versions

[justlevine]

What?

• Followup to ci: pin NPM deps and ignore @wordpress from dependabot #831

This PR drops the @wordpress production dependencies to the versions that shipped in WordPress 7.0

Important

This PR is stacked on #831 which should be merged first.
Relevant diff: 23fd12f

Why?

@wordpress/dependency-extract-wordpress-plugin strips our production dependencies from the build, so to confirm we're not consuming incompatible functionality we want to lock them whenever possible.

How?

Removed the devDependencies section to prevent conflicts, and then ran wp-scripts packages-update --dist-tag=wp-7.0

Use of AI Tools

none

Testing Instructions

1. npm ci - confirm you can still install
2. npm run build - confirm building still works
3. npm run lint:js && npm run typecheck - confirm linting and typechecking still passes.

Screenshots or screencast

Before	After

Changelog Entry

Added - New feature.
Changed - Existing functionality.
Deprecated - Soon-to-be removed feature.
Removed - Feature.
Fixed - Bug fix.
Security - Vulnerability.
Developer - Development related updates.
Developer - Drop @WordPress dependencies to versions included in WordPress Core 7.0.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 75.50%. Comparing base (9db55ee) to head (23fd12f).

Additional details and impacted files

@@            Coverage Diff             @@
##             develop     #832   +/-   ##
==========================================
  Coverage      75.50%   75.50%           
  Complexity      2086     2086           
==========================================
  Files             99       99           
  Lines           8626     8626           
==========================================
  Hits            6513     6513           
  Misses          2113     2113           

Flag	Coverage Δ
unit	75.50% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[jeffpaul]

@justlevine with #831 merged in, can this PR come out of draft for review?

[justlevine]

@jeffpaul while feedback is welcome, it's not yet a "merge candidate" since we need to address those failing lints. (usually I keep these as draft until then as a signal that maintainers don't need to pay attention to it, but if there's a different flow you'd find more effective - WIP in title, a new label, etc - lemme know 🙏)

Status update

Most likely next step is to split the difference with

• 1 PR of all the deps that can be dropped with no code change,
• and then another where the errors are triaged (which are just upstream type fixes, what needs a hint, is there any actually non 7.0 usage we need to roll back)

This task isn't "owned" if anyone wants to pull out individual deps into a new PR or committing remediations directly on this branch, please go ahead, not stepping on my toes.