62791 : Could pre_render_block come later

[nirav7707]

Core Trac Ticket: https://core.trac.wordpress.org/ticket/62791

Adds a new pre_render_block_output filter that allows short-circuiting block rendering after context and data processing has been completed.

• Adds pre_render_block_output filter after render_block_context and WP_Block instantiation
• Receives the complete WP_Block instance with processed context and attributes
• Allows returning custom markup to bypass default rendering
• Maintains backward compatibility with existing filters

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

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

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