task: #3620349 Remove the dead drupal-libraries-sync.js script

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

What and why

Varbase 11 used to get six front-end libraries by running scripts/drupal-libraries-sync.js, a Node script that copied files out of node_modules/ into web/libraries/, driven by a drupal-libraries block plus six npm dependencies and a postinstall hook in package.json. That is replaced by Composer packages on Packagist, each required by the module or the varbase_* recipe that actually loads it: vardot/aos 2.3.4, vardot/jquery.fancytree 2.38.5, vardot/ckeditor5-media-embed-drupal 47.6.2, vardot/ace 1.44.0 and vardot/dropzone 5.9.3 (all type: drupal-library, all on Packagist), plus swagger-api/swagger-ui, which drupal/openapi_ui_swagger already required and which only needed an installer path.

This project's copy of scripts/drupal-libraries-sync.js (112 lines) was already dead before the Composer move: the source .gitlab-ci.yml has no job that runs it, and no package.json in the repository carries a drupal-libraries block for it to read. git grep -n drupal-libraries-sync 1.0.x returns only the script file itself.

This commit deletes the script. No behaviour changes.

Verified on a freshly installed Varbase 11.4.5 site in DDEV with the packages resolved from Packagist and no VCS repositories: 14/14 declared library files present, 10/10 assets HTTP 200, 7/7 Drupal libraries discovered with every asset resolving, status report green, and yarn install succeeds with none of the six npm library packages present.

A separate note for the maintainer

.gitlab-ci-local/expanded-gitlab-ci.yml still names the script, but that file is stale generated output — 9 jobs against the 8 in .gitlab-ci.yml, the extra one being a whole 🧩 (Drupal CMS) Install Educare site template pre-test job the source no longer has. It was committed once (commit b0ac6ad) and never regenerated.

Not fixed here, and it deserves its own issue: it should be regenerated or gitignored. Hand-editing generated output is worse than leaving it alone.

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