task: #3618301 Add quick smoke checks to the Drupal CMS install job in CI

Issue: https://www.drupal.org/project/horizonaid/issues/3618301

CI proved the Drupal CMS install was applied (the default theme) and then threw the site away, without ever asking whether that site actually serves. This adds a handful of cheap checks to 🧩 (Drupal CMS) Install Horizon Aid site template itself. The functional testing suite stays on the Varbase base only, by intent.

Changes in .gitlab-ci.yml, all inside the Drupal CMS install job, after the existing default-theme assertion:

• Serve the installed site with drush runserver and assert HTTP 200 on /, /user/login and /search.
• Assert drush status reports a successful bootstrap.
• Assert the recipe's content landed: non-zero node count and non-zero canvas_page count, via drush ev. Greater-than-zero, not a fixed total, so curating the content does not turn CI red.
• Assert nothing fatal was logged while the template was applied: drush watchdog:show --type=php --severity=Error comes back empty.
• Each failure prints its own reason, the job exits non-zero on any of them, and the webserver is stopped before the job reports.

Seconds, not minutes: no cucumber, no Playwright, no node. allow_failure: false, nothing masked, no || true around a check.

The earlier commits on this branch added a separate 🧪 varbase-e2e (Drupal CMS) lane that ran a two-bucket cucumber subset against the Drupal CMS site. That lane is removed at the maintainer's direction: Drupal CMS CI tests the install only, and the e2e suite runs against the Varbase project. Removed with it are the .cms_cache / .cms_test_cache cache wiring, the db_wait fragment, the horizonaid-cms-db.sql.gz dump and artifact, and the per-base changes to 📊 Create reports. The Varbase e2e lane and the report job are back to byte-identical with 1.0.x; the Drupal CMS install job keeps its own cmssite/composer.json and cmssite/package.json artifacts.

AI-Generated: Yes

Checkpoints:

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