Build: Fix redirect and error handling in performance results logging

[youknowriad]

Summary

• Replace https.request() with native fetch() in log-results.js
• Properly follow HTTP redirects (301/302)
• Exit with non-zero code on non-2xx responses

Problem

The performance results logging script would silently succeed even when the API returned a redirect or error response, causing performance results to be lost without any indication in CI.

Solution

Use native fetch() (Node 18+) which automatically follows redirects and check response.ok to properly fail on error responses.

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

---

🤖 Generated with Claude Code

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

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.

[youknowriad]

This actually doesn't solve the issue as it is, follow redirect doesn't work as intended for "post" request (the body is dropped). Let me try to figure out an alternative (maybe use the non redirected url directly)

[youknowriad]

These changes avoid the redirects

[youknowriad]

Ok I think this works now, only way to actually test though is to commit.

[mcsf]

LGTM, let's test.