feat: #3621788 Release Varbase Project 11.0.7

Issue: #3621788

Release Varbase Project 11.0.7, the template that ships Varbase 11.0.0 — the first stable release of the 11.0.x line — and the three site templates at 1.0.1.

What changed

• composer.json: version 11.0.x-dev → 11.0.7, and vardot/varbase and vardot/varbase-patches 11.0.x-dev → ~11.0.0.
• README.md: badge → 11.0.7.
• CHANGELOG.md: a 11.0.7 entry, plus a backfilled 11.0.6 entry (see below).

No drupal/varbase_* requirements are touched, because there are none left: !99 (merged) removed them, restoring the shape tag 11.0.6 had, where the only Varbase requirements are the two vardot/* packages.

No dev constraint remains in require, asserted programmatically before committing.

Why the pins are ~11.0.0 and not ~11.0.7

Tag 11.0.6 pins vardot/varbase: ~11.0.0 and vardot/varbase-patches: ~11.0.0, and 10.1.4 pins ~10.1.0. The tilde floor stays at the .0 of the minor, so the released tag keeps taking patch releases of the profile and the patches package. vardot/varbase-patches is currently at 11.0.42, comfortably inside that range.

The backfilled 11.0.6 CHANGELOG entry

CHANGELOG.md on the branch started at # 11.0.5, and the README badge still read 11.0.5. 11.0.6 was released without updating either, so writing a 11.0.7 entry titled "since 11.0.6" would have left a hole in the file. I derived an 11.0.6 entry from the eleven commits between the 11.0.5 and 11.0.6 tags (Workflow Modeler tests, header search coverage, the issue and merge request templates, the move to Varbase E2E, and the two CI performance fixes) so the history is continuous. Release plumbing is excluded, as usual.

If you would rather the backfill were a separate change, say so and I will split it out.

Checkpoints

• Addition/Change/Update/Fix
• Testing to ensure no regression
• Reviewed by a human
• Code review by maintainers
• Release

This work was done with the help of AI, and reviewed by a human. Per the Drupal AI policy.