Migrate CSS and classes to container queries for linked pipelines (1)

What does this MR do and why?

Migrate CSS and classes to container queries for linked pipelines

This change migrates classes in the linked pipelines (downstream and upstream) pipeline that depended on media queries.

References

• Issue: https://gitlab.com/gitlab-org/gitlab/-/issues/566956+
• Next MR: Migrate to container queries for pipeline detai... (!203681 - closed)

Screenshots or screen recordings

No changes expected. Test of both upstream and downstream pipelines in small and regular viewports:

How to set up and validate locally

1. Define a trigger pipeline.

ci yml example

stages:          
  - build
  - test
  - deploy
  - downstream

build-job:       
  stage: build
  script:
    - echo "Compiling the code..."
    - echo "Compile complete."

unit-test-job:
  stage: test 
  script:
    - echo "Running unit tests... This will take about 60 seconds."
    - sleep 1
    - echo "Code coverage is 90%"

lint-test-job:
  stage: test
  script:
    - echo "Linting code... This will take about 10 seconds."
    - sleep 1
    - echo "No lint issues found."

deploy-job:
  stage: deploy
  environment: production
  script:
    - echo "Deploying application..."
    - echo "Application successfully deployed."

downstream-job:
  stage: downstream
  trigger:
    include:
      - project: 'my-group/my-project' # NOTE: this project should exist
        ref: 'main'
        file: .gitlab-ci.yml

2. Run and visit the pipeline
3. Expand/collapse the downstream pipeline
4. Visit the downstream pipeline
5. Expand/collapse the upstream pipeline

MR acceptance checklist

Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Related to #567314