refactor: #3618244 Remove the Drupal CMS wiring script

Removes the Drupal CMS wiring script and everything that only existed to serve it.

Issue: https://www.drupal.org/project/educare/issues/3618244

Depends on !38 (merged) (!38 (merged)). This branch is cut from 3618244-move-the-varbase, so !38 (merged) should merge first.

What was removed

539 deletions across 6 files:

• scripts/drupal-cms-wiring.php — the script itself.
• scripts/assets/drupal-cms.composer.json — the composer values it merged into a root composer.json.
• scripts/assets/drupal-libraries.package.json — the package.json values it merged.
• scripts/drupal-libraries-sync.js — copied into the project root by the script.
• .gitlab-ci.yml — the 🧩 (Drupal CMS) Install Educare site template job that ran it, plus the .cms_cache anchor only that job used.
• scripts/README.md — the "Wire a Drupal CMS project for Educare" section.

scripts/assets/ no longer exists.

Why

Educare is installed on a Varbase 11 base, which already carries vardot/varbase-patches and the rest of the wiring this script reproduced for a plain drupal/cms codebase.

Trade-off, stated plainly

This removes the only CI job that exercised Educare off a non-Varbase base, and with it the composer show vardot/varbase-patches assertion. After this MR, vardot/varbase-patches is not referenced by the recipe at all.

Verification

• git grep finds no remaining reference to the script, its assets, cmssite or drupal/cms anywhere in the tree. ESLint lints only cucumber.js and tests/step-definitions/, so removing the JS file does not affect it.
• Local gitlab-ci-local on this branch, all PASS: 📦 Composer validate, 📐 YAML lint, 🔤 Cspell, 🟨 ESLint, 🧩 Cucumber dry-run, 📦 (Varbase) Install Educare site template (11 min). The pipeline still resolves to 8 jobs with every YAML anchor intact.
• !38 (merged)'s own pipeline finished with all 24 jobs green: https://git.drupalcode.org/project/educare/-/pipelines/930318

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