ci: update test composes [citest_skip]

[mirecheck]

Update test composes for GitLab CI.

Summary by Sourcery

Update CI test matrix to use newer RHEL 9 and 10 nightly composes for 'Next' and 'CurrentRelease' pipelines.

CI:

• Bump RHEL 10 'Next' and 'CurrentRelease' CI jobs to use 10.3 and 10.2 nightly composes respectively.
• Bump RHEL 9 'Next' and 'CurrentRelease' CI jobs to use 9.9.0 and 9.8.0 nightly composes respectively.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

.gitlab-ci.yml test matrix updated to point RHEL 9 and 10 CI jobs at newer nightly composes and corresponding distro identifiers for "Next" and "CurrentRelease" variants.

Flow diagram for COMPOSE_NAME to updated RHEL nightly mappings in .gitlab-ci.yml

flowchart TD
  Start[Start CI job]
  CName[Read COMPOSE_NAME]

  Start --> CName

  CName -->|Rhel10Next| R10NextVars[Set variables for Rhel10Next]
  CName -->|Rhel10CurrentRelease| R10CurVars[Set variables for Rhel10CurrentRelease]
  CName -->|Rhel9Next| R9NextVars[Set variables for Rhel9Next]
  CName -->|Rhel9CurrentRelease| R9CurVars[Set variables for Rhel9CurrentRelease]

  subgraph Rhel10NextConfiguration
    R10NextVars --> R10NextTF[TF_COMPOSE = RHEL-10.3-Nightly]
    R10NextVars --> R10NextTMTDev[TMT_DEVELOPMENT = true]
    R10NextVars --> R10NextTMT[TMT_DISTRO = rhel-10.3]
    R10NextVars --> R10NextPCSBranch[PCS_BRANCH = main]
    R10NextVars --> R10NextPCSUrl[PCS_ARTIFACTS_URL uses COMPOSE_NAME and PCS_BRANCH]
  end

  subgraph Rhel10CurrentReleaseConfiguration
    R10CurVars --> R10CurTF[TF_COMPOSE = RHEL-10.2-Nightly]
    R10CurVars --> R10CurTMT[TMT_DISTRO = rhel-10.2]
    R10CurVars --> R10CurPCSBranch[PCS_BRANCH = main]
    R10CurVars --> R10CurPCSUrl[PCS_ARTIFACTS_URL uses COMPOSE_NAME and PCS_BRANCH]
  end

  subgraph Rhel9NextConfiguration
    R9NextVars --> R9NextTF[TF_COMPOSE = RHEL-9.9.0-Nightly]
    R9NextVars --> R9NextTMTDev[TMT_DEVELOPMENT = true]
    R9NextVars --> R9NextTMT[TMT_DISTRO = rhel-9.9]
    R9NextVars --> R9NextPCSBranch[PCS_BRANCH = pcs-0.11]
    R9NextVars --> R9NextPCSUrl[PCS_ARTIFACTS_URL uses COMPOSE_NAME and PCS_BRANCH]
  end

  subgraph Rhel9CurrentReleaseConfiguration
    R9CurVars --> R9CurTF[TF_COMPOSE = RHEL-9.8.0-Nightly]
    R9CurVars --> R9CurTMT[TMT_DISTRO = rhel-9.8]
    R9CurVars --> R9CurPCSBranch[PCS_BRANCH = pcs-0.11]
    R9CurVars --> R9CurPCSUrl[PCS_ARTIFACTS_URL uses COMPOSE_NAME and PCS_BRANCH]
  end

  R10NextPCSUrl --> End[Run tests with selected compose]
  R10CurPCSUrl --> End
  R9NextPCSUrl --> End
  R9CurPCSUrl --> End

Loading

File-Level Changes

Change	Details	Files
Bump RHEL 10 CI composes and distro identifiers for Next and CurrentRelease pipelines.	Update Rhel10Next TF_COMPOSE from 10.2 nightly to 10.3 nightly and align TMT_DISTRO from rhel-10.2 to rhel-10.3 while keeping PCS branch and artifacts URL unchanged Update Rhel10CurrentRelease TF_COMPOSE from 10.1 nightly to 10.2 nightly and align TMT_DISTRO from rhel-10.1 to rhel-10.2, preserving existing PCS configuration	.gitlab-ci.yml
Bump RHEL 9 CI composes and distro identifiers for Next and CurrentRelease pipelines.	Update Rhel9Next TF_COMPOSE from 9.8.0 nightly to 9.9.0 nightly and TMT_DISTRO from rhel-9.8 to rhel-9.9, leaving PCS branch and artifacts URL as-is Update Rhel9CurrentRelease TF_COMPOSE from 9.7.0 nightly to 9.8.0 nightly and TMT_DISTRO from rhel-9.7 to rhel-9.8, with no other CI configuration changes	.gitlab-ci.yml

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey - I've left some high level feedback:

• The PCS_ARTIFACTS_URL and some other variables are repeated verbatim across all rules; consider using YAML anchors/aliases or a shared template to reduce duplication and make future version bumps less error-prone.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- The `PCS_ARTIFACTS_URL` and some other variables are repeated verbatim across all `rules`; consider using YAML anchors/aliases or a shared template to reduce duplication and make future version bumps less error-prone.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 90.92%. Comparing base (d1f3c0c) to head (b26a034).
⚠️ Report is 19 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #366   +/-   ##
=======================================
  Coverage   90.92%   90.92%           
=======================================
  Files          19       19           
  Lines        1212     1212           
=======================================
  Hits         1102     1102           
  Misses        110      110           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.