TINY-11177: Vastly improve remote testing

[TheSpyder]

Related Ticket: TINY-11177

Description of Changes:

• Remote testing was slow because bedrock sent session POST requests to /start before each it block, and then again to /results after each it block. It would wait for these requests to finish before continuing.
• /start is now sent at startup and after every 50 tests. This can be made larger if we find it's still too slow.
• /results is now only sent for failure and skip, not pass.
• The bedrock UI doesn't block on these status requests anymore, it just throws them into an array and uses Promise.all() at the very end to wait for them.
• Unfortunately the bedrock CLI console HUD depended on receiving these status updates, so I had to adjust it to account for the missing reports.
• The bedrock HTML page now has a fake icon to remove the favicon.ico request which probably also slowed things down.
• A proper keep-alive header is now set, instead of using the default 5 seconds which was causing occasional 502 Bad Gateway errors.
• Reverted TINY-10708: Suppress bedrock logs in remote testing #142 which was designed to solve this problem but server-side was the wrong answer.

Pre-checks:

• Changelog entry added
• package.json versions have not been changed (done by Lerna on release)
• Tests have been added (if applicable)

Before merging:

• Ensure internal dependencies are on appropriate versions
  • For stable releases, all dependencies must be stable
  • For release candidates, all dependencies must be release candidates or stable

[spocke]

How does this affect junit reporting would the in flight requests make them in random order or would things be skipped.

[TheSpyder]

I posted in slack that this destroys JUnit reporting. Ideas for how to fix:
https://cksource.slack.com/archives/C04KXE6QUTX/p1724022794632699?thread_ts=1723766938.410059&cid=C04KXE6QUTX

[TheSpyder]

For the record, JUnit records are long since fixed.