Add old_slug_redirect_status filter to allow customizable HTTP redirect codes

[himanshupathak95]

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

This PR addresses Trac Ticket #52737 by introducing the old_slug_redirect_status filter. Previously, wp_old_slug_redirect() hardcoded the redirect status to 301, preventing developers from issuing temporary redirects (302) or other custom HTTP status codes when a post's slug changes.

• Introduced the old_slug_redirect_status filter in src/wp-includes/query.php.
• Passed the $id (Post ID) as the second parameter to allow conditional redirects based on post properties.

Example -

// Example: Use 302 for WooCommerce products only
add_filter( 'old_slug_redirect_status', function( $status, $post_id ) {
    if ( get_post_type( $post_id ) === 'product' ) return 302;
    return $status;
}, 10, 2 );

• Allowed returning a falsy value to entirely abort the redirect.

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

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.