Add test filter standardisation for hip-tests

[dileepr1]

Summary

Add test-filter standardisation for hip-tests, mirroring the pattern
established by TheRock#4694 (rccl).
Paired with the rocm-systems branch
users/dravindr/tf_hiptests (rocm-systems#6315),
which wires tier (quick / standard / comprehensive / full) and
arch-exclude tags into hip_test_config.hh at build time and exposes
them as CTest labels via
catch_discover_tests(ADD_TAGS_AS_LABELS ... DISCOVERY_MODE PRE_TEST).

Three commits:

1. Add test filter standardisation for hip-tests

   • fetch_test_configurations.py: route hip-tests test_script to the
     generic test_runner.py, which now drives ctest -L <tier> from
     the installed Catch2 directory using the labels baked into the
     binaries.
   • test_runner.py: add hip-tests COMPONENT_OVERRIDES:
     • test_dir = share/hip/catch_tests (not bin/<component>/).
     • LD_LIBRARY_PATH = ROCM_PATH/lib so the Catch2 binaries can
       dlopen HIP.
   • artifact-core-hiptests.toml already includes share/hip/**, so
     the install-tree CTestTestfile.cmake and Catch2 binaries are
     already bundled — no toml change needed.

2. `test_runner`: honour `<gfx_pattern>[_]_exclude` labels

   • Generalise exclude-label handling so per-arch / per-OS
     known-broken tests can be expressed purely in
     test_categories.yaml without baking the convention into
     individual component runners.
   • Recognised label shapes:
     • `gfx950_exclude` — OS-agnostic, exact arch
     • `gfx94X_linux_exclude` — Linux-only, wildcard arch
     • `gfx110X_windows_exclude` — Windows-only, wildcard arch
   • New helper `find_matching_arch_exclude_labels()` parses each
     `*_exclude` label with a strict regex anchored to `gfx<...>`,
     skips labels whose OS suffix does not match the current host, and
     uses the existing `find_matching_gpu_arch()` wildcard semantics.
   • `build_ctest_command()` OR's matching labels into the same `-LE`
     regex used for `{category}_exclude`, preserving
     "any-match excludes" semantics.
   • Plain `_exclude` labels and other components' existing
     `*_exclude` labels are unaffected.

3. `test_runner`: strip `(variant)` suffix from `TEST_COMPONENT`

   • The hip-tests Windows CI job sets `TEST_COMPONENT="hip-tests (PAL)"`
     (and optionally `"hip-tests (ROCR)"`) from
     `fetch_test_configurations.py`, where `(PAL)` / `(ROCR)` are
     matrix-variant tags rather than distinct test components. The
     runner passed those literal strings into both
     `COMPONENT_DIR_MAPPING` and `COMPONENT_OVERRIDES` lookups,
     neither of which keys on the variant suffix, so the override
     silently did not apply and `TEST_DIR` fell back to the
     non-existent `build\bin\hip-tests (PAL)`.
   • Normalise the lookup by stripping a trailing parenthesised suffix
     (`\s*\([^)]\)\s$`) before the mapping / overrides lookups.

Companion PR

• rocm-systems: Add test filter standardization to hip-tests rocm-systems#6315

Test plan

• Linux CI green on `hip-tests` job (gfx94X / gfx950 paths exercise
  the new `__exclude` label handling).
• Windows CI green on `hip-tests (PAL)` and `hip-tests (ROCR)`
  jobs (exercises the variant-suffix strip).
• Sanity-check that other components' existing `*_exclude` labels
  still parse the same way.

Made with Cursor