Update uuid dependency

[anomiex]

What?

Packages are updated to the latest version, 14.0.0. The monorepo root is updated to 11.1.1, which is the latest version that still supports CommonJS.

Why?

Upstream has deprecated all versions of uuid before 11, and notes that 11 will likely be deprecated in 2028.

How?

... By updating the version numbers in package.json files.

Testing Instructions

There should be no functional changes due to this PR.

Testing Instructions for Keyboard

N/A

Screenshots or screencast

N/A

Use of AI Tools

None

[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: anomiex <bjorsch@git.wordpress.org>
Co-authored-by: manzoorwanijk <manzoorwanijk@git.wordpress.org>
Co-authored-by: jsnajdr <jsnajdr@git.wordpress.org>

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

[anomiex]

@manzoorwanijk Care to review? Or suggest who should? Thanks! 🙂

[manzoorwanijk]

This should be fine. Let us wait for CI to be happy.

[anomiex]

Looks like these E2E tests are broken in trunk too.

[jsnajdr]

The monorepo root is updated to 11.1.1, which is the latest version that still supports CommonJS.

Why do we need to do this, because of Jest?

[anomiex]

Because various files in the root use require( 'uuid' ), I left it at the latest version supporting CommonJS.

• gutenberg/bin/plugin/lib/utils.js

  Line 8 in 5c11c92

  const { v4: uuid } = require( 'uuid' );

• gutenberg/test/e2e/specs/editor/blocks/classic.spec.js

  Line 7 in 5c11c92

  const { v4: uuid } = require( 'uuid' );

• gutenberg/test/e2e/specs/editor/blocks/cover.spec.js

  Line 7 in 5c11c92

  const { v4: uuid } = require( 'uuid' );

• gutenberg/test/e2e/specs/editor/blocks/gallery.spec.js

  Line 7 in 5c11c92

  const { v4: uuid } = require( 'uuid' );

• gutenberg/test/e2e/specs/editor/blocks/image.spec.js

  Line 7 in 5c11c92

  const { v4: uuid } = require( 'uuid' );

• gutenberg/test/e2e/specs/editor/various/big-image-size-threshold.spec.js

  Line 7 in 5c11c92

  const { v4: uuid } = require( 'uuid' );

• gutenberg/test/e2e/specs/editor/various/upload-save-lock.spec.js

  Line 7 in 5c11c92

  const { v4: uuid } = require( 'uuid' );

On the other hand, if you're using node 20.19.0+, it may be possible to use uuid v14 despite it being esm-only thanks to the unflagging of the require(esm) feature in that version. Jest or other stuff may still have issues with it though. I'll leave experimenting with that for someone else.

[manzoorwanijk]

Linting is broken. Fix in #77888