Allow for CORS requests to api.wordpress.org to pass

[dd32]

What is this PR doing?

Fixes CORS requests to WordPress.org, even with custom headers.

What problem is it solving?

See #1003

This is a workaround until https://make.wordpress.org/systems/2024/02/07/cors-requests-for-api-wordpress-org/ is resolved.

How is the problem addressed?

Altering the URI that fetches to api.wordpress.org make, to replace requests to /path/ to /path/index.php to allow for OPTIONS requests to reach PHP.

Testing Instructions

Untested. Make sure upon booting no networking errors are encountered.

[bgrgicak]

@dd32 this PR doesn't work for me, I still get CORS errors when I open the plugins list.

[dd32]

@bgrgicak Thanks! I wasn't actually able to properly test this.

I guess this goes back to #933 then - That custom header shouldn't be included with all outgoing HTTP requests.

[bgrgicak]

Looks like this custom header is causing the issue.

If I remove it on trunk, requests work again.

[bgrgicak]

@dd32 this PR should fix the issue #1010

[adamziel]

Thank you so much @dd32! I somehow assumed the CORS setup on w.org must have changed when it was a Playground PR all along. 🙌 I'll go ahead and merge #1010 to remove the custom header, but this PR still seems to makes sense regardless or #1010. Would you recommend merging it anyway?

[dd32]

Would you recommend merging it anyway?

Kind of; but at the same time, if things are working right now... might be better to just leave it as-is.