Test Horizon Aid on Drupal CMS only, and rename the test job to functional testing

Problem/Motivation

The pipeline builds two hosts in pre-test:

• 📦 (Varbase) Install Horizon Aid site template — builds drupal/varbase_project:11.0.x-dev
• 🧩 (Drupal CMS) Install Horizon Aid site template — builds drupal/cms

and the whole 🧪 varbase-e2e matrix (18 parallel buckets) runs against the Varbase one. Horizon Aid is a Drupal CMS site template: Drupal CMS is the base it is shipped for and the base people install it on, so that is the base the functional suite should exercise. Building both doubles every pre-test minute and leaves the shipped base untested by the suite.

Separately, the pipeline is currently red on 1.0.x itself, and not because of any recipe change. Pipeline 953793, running on cb331f3 (plain 1.0.x), fails BOTH install jobs at composer require, before any Drupal command runs:

In Patches.php line 288:
  No available patcher was able to apply patch
  https://raw.githubusercontent.com/vardot/varbase-patches/refs/heads/patches/canvas--2026-07-26--3560889--mr-1425.patch
  to drupal/canvas

That patch (fix: #3560889 JsComponent crash ... relative example URLs) targets src/Plugin/Canvas/ComponentSource/JsComponent.php and no longer applies to drupal/canvas 1.11.0 — the hunk's context has drifted (it only applies with patch -p1 at fuzz 1 and offset 72 lines, which the stricter composer-patches patchers reject). Both install jobs die there.

The name varbase-e2e is also the tool, not the job's purpose; the job runs the functional acceptance suite.

Steps to reproduce

1. Open the pipeline for commit cb331f3 on the 1.0.x branch of Horizon Aid (pipeline 953793), or push any commit to 1.0.x.
2. Watch the pre-test stage: both 📦 (Varbase) and 🧩 (Drupal CMS) install jobs fail at composer require with the Patches.php line 288 error above, before any Drupal command runs.
3. Read the 🧪 varbase-e2e job definition: its needs points at the Varbase host job, so the 18-bucket matrix never exercises the Drupal CMS base the template ships for.

Proposed resolution

1. Remove the 📦 (Varbase) Install Horizon Aid site template job.
2. Make 🧩 (Drupal CMS) Install Horizon Aid site template the single host build, and give it what the test jobs need: prepare the installed site for deterministic testing (uninstall antibot and autosave_form, raise the user.flood limits, set system.logging error_level all), seed the per-role testing users, install the functional suite and Chromium, and dump the database as the horizonaid-db.sql.gz artifact.
3. Point the test job at that job, rename it 🧪 Functional testing, and move SITE_DIR / WEB_ROOT and the build cache from testsite/ to cmssite/ (drush lives in vendor/bin on a drupal/cms root, not bin/).
4. Drop the vardot/varbase-patches wiring from the pipeline. The template installs green on stock Drupal CMS with no patches of any kind, so requiring the curated patch set only coupled this pipeline to its drift — which is exactly what is failing the build today.

Verified locally on plain drupal/cms (Drupal core 11.4.6, drupal/canvas 1.11.0, PHP 8.4, DDEV, MariaDB, no patches):

• drush site:install recipes/horizonaid → exit 0, zero warnings, zero PHP errors logged.
• drush site:install drupal_cms_installer installer_site_template_form.add_ons=horizonaid → exit 0, zero warnings.
• The rewritten .gitlab-ci.yml is accepted by the GitLab CI lint API (valid: true; the only warnings are the pre-existing deprecated retry: when: stuck_or_timeout_failure values, untouched by this change).

Note both of those installs also require the fix in #3622092, and the warning clean-up in #3621847 and #3621848; this issue is only about which host CI builds and what the test job is called.

Note for the queue: the stale canvas--2026-07-26--3560889--mr-1425.patch is a vardot/varbase-patches problem and needs its own fix there (re-roll against canvas 1.11.0, or drop it if superseded upstream). Dropping the patch stack from this pipeline unblocks Horizon Aid but does not fix varbase-patches itself.

AI-Generated: Yes — drafted with Claude Code (Claude Opus 5). The installs above were run locally by a human, and the pipeline file was checked against the GitLab CI lint API.

Remaining tasks

• ✅ File an issue
• ❌ Addition/Change/Update/Fix
• ❌ Testing to ensure no regression
• ❌ Automated unit/functional testing coverage
• ➖ Developer Documentation support
• ➖ User Guide Documentation support
• ➖ UX/UI designer responsibilities
• ➖ Accessibility and Readability
• ❌ Reviewed by a human
• ❌ Code review by maintainers
• ❌ Full testing and approval
• ❌ Credit contributors
• ❌ Review with the product owner
• ❌ Update Release Notes
• ❌ Release

User interface changes

• N/A

API changes

• N/A

Data model changes

• N/A

Release notes snippet

• N/A