Update package-lock lockfile version

[sirreal]

Update the package-lock.json file to the v3 format:

3: Only the new lockfile information introduced in npm version 7. Smaller on disk than lockfile version 2, but not interoperable with older npm versions. Ideal if all users are on npm version 7 and higher.

Given the engines and engine-strict setting, npm versions earlier than 7 should not be used and there should be no downsides to this change:

wordpress-develop/package.json

Lines 9 to 12 in 90d2429

	"engines": {
	"node": ">=20.10.0",
	"npm": ">=10.2.3"
	},

wordpress-develop/.npmrc

Line 2 in 90d2429

engine-strict = true

Similar PR for Gutenberg: WordPress/gutenberg#65923

The lockfile goes from 2124789 to 1175664 bytes, around 950kb smaller.

Trac ticket: https://core.trac.wordpress.org/ticket/62190

---

This Pull Request is for code review only. Please keep all other discussion in the Trac ticket. Do not merge this Pull Request. See GitHub Pull Requests for Code Review in the Core Handbook for more details.

[github-actions]

Test using WordPress Playground

The changes in this pull request can previewed and tested using a WordPress Playground instance.

WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser.

Some things to be aware of

• The Plugin and Theme Directories cannot be accessed within Playground.
• All changes will be lost when closing a tab with a Playground instance.
• All changes will be lost when refreshing the page.
• A fresh instance is created each time the link below is clicked.
• Every time this pull request is updated, a new ZIP file containing all changes is created. If changes are not reflected in the Playground instance,
  it's possible that the most recent build failed, or has not completed. Check the list of workflow runs to be sure.

For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation.

Test this pull request with WordPress Playground.

[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.

Core Committers: Use this line as a base for the props when committing in SVN:

Props jonsurrell, desrosj.

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

[desrosj]

Hey @sirreal!

This makes sense to me, but we need a Trac ticket to attach it to. I was going to use Core-61530, but that's more for test tooling and test improvements. I think a separate ticket for this would be fine. Feel free to assign the ticket to me in Trac!

If you could create that, add it to this description to link the two, and make any necessary adjustments after the beta 2 package bumps, I can get this committed.

[sirreal]

I was going to use Core-61530, but that's more for test tooling and test improvements. I think a separate ticket for this would be fine.

I had similar thinking, thanks for confirming. I've created #62190.

[sirreal]

I've merged trunk and then went through the process of resetting the lockfile and applying the version change again to ensure it's up to date.

[desrosj]

Merged in https://core.trac.wordpress.org/changeset/59205.