[thrix]

Packit gets the results URL of a Testing Farm run only after Testing Farm reports back. Until then, the run detail page and the runs table show the pipeline ID with no link.

This adds getTestingFarmResultsUrl(), which falls back to https://api.dev.testing-farm.io/v0.1/requests/<pipeline_id> when web_url is missing. The status label on the run detail page and the pipeline ID link in the runs table use it. A run without a pipeline ID (not submitted yet) gets no link.

web_url is now typed as string | null, since packit-service stores None until the results arrive.

The API URL matches the TESTING_FARM_API_URL default in packit-service. If a deployment submits to another Testing Farm instance, this constant needs to follow.

Fixes #527

Generated-by: Claude Code

[centosinfra-prod-github-app]

Build succeeded.
https://gateway-cloud-softwarefactory.apps.ocp.cloud.ci.centos.org/zuul/t/packit-service/buildset/0d39ff956f6142d182d39aebf275dcda

✔️ pre-commit SUCCESS in 1m 40s

[betulependule]

I personally prefer this version over fullsend's #552.

It's overall more consistent, includes tests and has a guard for the possibillity of <pipeline_id> not being defined. This can happen when the Testing Farm job is new doesn't have an ID assigned just yet, and this PR makes sure to check that it is defined before adding a link constructed based on the value of the ID. If this check weren't present, it would add a broken link.

This implementation makes it so that when the status field is clicked (fedora-43-x86_64), it redirects to https://api.dev.testing-farm.io/v0.1/requests/<pipeline_id> when the job is still queued.

I personally didn't find anything that looks broken. Perhaps it would make sense to also change pipeline_id: string; to pipeline_id: string | null; in frontend/src/apiDefinitions.ts, but that's a nitpick.