Update Connector CI to report status to Github Status Checks not comments

[evantahler]

Some connector developers are wary of pushing often to Github because CI spams comments onto their PRs, especially if you are working on multiple connectors. This makes seeing PR reviews and comments hard.

Right now, CI leaves both a comment and a Github Status check (1,2) for every test (from #29213)

Now that we have excellent CI reports (e.g.), I believe that the need for the Github comment is less than it used to be. We should change the URL in the Github status to point to this report, rather than the action. This gives the connector developer the information they need to investigate a failure, without clogging up the PR history.

If we cannot change the status report URL, then we should be updating the existing CI comment rather than making a new one. This would serve the same goal of spam reduction.

[pedroslopez]

grooming:

• Rename Connectors CI to Connectors CI (trigger)
• Connectors CI (trigger) details -> stick to going to the github action run
• Connectors CI tests details -> Dagger Cloud
• Individual test step details -> HTML report
• HTML report continually updated upon step start/completion
  • Q: how do logs fit into the continuously updated report?
• Check status for individual test step should go red immediately upon a failure
• Kill the PR comment

[alafanechere]

Moving this to the Connectors CI/CD new features as the task force is over.

[evantahler]

I'd like to bring this back as part of the DX work we are doing in Q4 if there's time (cc @bnchrch / @alafanechere ). It's still rather annoying to get an email/slack for every test run

[evantahler]

Grooming:

• Remove the comments
• Update the GHA per-connector status links to point to a new root HTML report that links to all the sub-connector builds

[alafanechere]

I disable test reports in comments in PR #31871 .
I'll opened a different issue (#31872) to create global html reports.
It's a bit more complex to implement currently because we don't have a GlobalContext , reports are attached to PipelineContext that are per connector. PipelineContexts are not attached to a higher level object that can gather all of them (and their reports).