Update the pinned gutenberg hash

[desrosj]

This updates the pinned gutenberg repository hash from WordPress/gutenberg@7b7fa2b to WordPress/gutenberg@9b81440.

Included Changes

The following changes are included in this update:

• Use V2 Yjs methods for HTTP Polling (Use V2 Yjs methods for HTTP Polling gutenberg#76304)
• Plugin: Include Icons assets in ZIP (Plugin: Include Icons assets in ZIP gutenberg#75866)
• Ensure consistent, repeatable build results when inlining WASM files via wasmInlinePlugin (Ensure consistent, repeatable build results when inlining WASM files via wasmInlinePlugin  gutenberg#76113)
• Account IS_WORDPRESS_CORE is set. (Check for IS_WORDPRESS_CORE before npm_package_config_IS_WORDPRESS_CORE gutenberg#76334)
• Block Visibility: Add fetchpriority=auto to IMG tags in blocks with conditional viewport visibility to prevent potential erroneous high loading priority (Block Visibility: Add fetchpriority=auto to IMG tags in blocks with conditional viewport visibility to prevent potential erroneous high loading priority gutenberg#76302)

Trac ticket: Core-64595.

Use of AI Tools

No use of AI.

---

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]

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

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

[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

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

[desrosj]

Merged in r61870.