- Show task ID in page header.

In order to make the tests reproducible and consistent, the `TZ`
environment variable is fixed to Europe/Prague for tests.

Display real data in "Build summary", "Active tags" and "Tagging
history" tabs.

Load information on the artifact specified by user in the URL
dynamically. This allows, among other things, to show the correct NVR, gating
tag, gating status and task ID in the page header.

Refactor the `isResultWaivable` and `isResultMissing` functions so that
they're applicable to any state type.

Display names and statuses of known test results for a given artifact as
they're stored in the database.

Interpret `NEEDS_INSPECTION` and `NOT_APPLICABLE` outcomes from Greenwave as
failed for required tests. This makes them appear in the topmost section
of the results table with the rest of the failed tests.

Add the blue info icon for the `info`, `needs_inspection` and
`not_applicable` statuses.

Reference: OSCI-4469

Make the waive button component for testcase accept the testcase name
instead of the whole state type. This disentangles the details of the
state type from the implementation of the button and makes the
control/data flow simpler in some places.

Being waived is seldom a useful distinct status – even when a test is
waived, we might still want to know what its original outcome was.
Therefore, remove the `waived` status and instead use a boolean flag
wherever we need to know the waive status, e.g. in the `TestStatusIcon`
component in this case.

Move conditional children components into function-level variables to
simplify the JSX chunks a bit.

Show the "Known issues" tab in the details drawer with the list of
issues as provided by CI maintainers. If no known issues have been
entered, hide the tab.

Move the new test results page to the primary URL, i.e. the
`/artifact/:type/:search/:value` route. Move the old page to
`/resultsold/...`, for example `/resultsold/brew-build/aid/53823788`.

The page only displays the first results for now, this will be extended
later.

Show test description provided by CI maintainers via custom metadata, if
available.

Add functions to extract gating tag and isseuer name from artifact, if
available.

- Allow the new results page to display results for all supported
  artifact types – RPM (Koji/Brew) builds, as well as module (MBS)
  builds, containers builds, composes, etc.
- Show detailed build metadata for module builds.
- Show Components tab for module builds and do not query for related
  advisories as module builds are not supported.

Generalize the `TagsList` component to be able to display Koji taks for
module builds as well.

Include the `WaiveForm` and `ToastAlertGroup` components in the new
results page so that the waiving UI works as expected.

Pass the whole `CiTest` to individual results table row components to
reduce repetition and remove the newly redundant props.

Use already existing components to display test cases within a suite and
their logs, test phases, etc.

Moreover, do a little refactoring for clarity and composability by
moving some chunks into names variables or functions.

Removed several outdated TODOs and fix those that are easy to fix.

Similar to the old behavior showing the artifact name and gating status,
if available.

We know that a test is missing thanks to Greenwave, but we do not have
any contact-related metadata coming from that channel, so we have to
pull contact metadata on an as-needed basis if the test is missing.

Make sure to store the requested focus test so that we can look it up
later, once all the tests have been loaded. This ensures that if you
select a test and refresh the page, it will expand automatically. This
was broken previously because the `useEffect()` hook only runs on first
render and when the query parameters change. When this happens at page
load, the `tests` variable is not yet populated becuse the query has not
finished yet. Therefore the correct test could not have been looked up
at this point in time.

Adjust the search results table according to the UXD mock-up. Use
a minimalist table with clickable rows that take you to the
single-artifact view instead of a table with various expandable rows.

Pagination is not yet implemented in this version.

Clean up code a bit without changing behaviour.

Refactor the `ArtifactsListNew` component to make it pure and reusable
across different scenarios. Move the `useQuery()` call out to the parent
component and insert a business-logic component between the list and
the `PageByFilters` component.