Dagger Dashboard URL in GHA is incorrect

[bnchrch]

Problem

Often the Dagger dashboard URL in the GHA log did not match that in our dagger-log.txt file.

From @alafanechere
We get a Dagger URL for every dagger client instantiation (dagger session).
In our pipelines, when using manual workflow dispatch, we instantiate 2 clients: one for the git diff operation to spot modified files on the remote branch (at the airbyte-ci command group level), another to run the main pipeline (at the test/publish command level).
This is why you can occasionally spot different URLs in the GHA logs vs Dagger logs.
The URL in the dagger logs url should always be the one of the main pipeline.

It’d indeed be more convenient to get this URL in the HTML report but the dagger URL logging is logged by the Dagger SDK. From the client, there’s no way to get this URL.
We could add a logic that scans the Dagger logs to parse this url and add it to the report.

[bnchrch]

grooming:

• first url relates to the git diff
• we do not have access to the correct url at HTML build time
• Lets direct users to the dagger dashboard with commit prefiltered e.g. https://alpha.dagger.cloud/runs?filter=github.com%2Fpr.head:35ee441ef4ad18ccae1116171ebe13877d63543c

[bnchrch]

closing in favor of #27863