Issue #3621622: Set the recipe version to 1.0.1 and pin every dependency to its released version

Release merge request for Varbase Starter 1.0.1.

Makes drupal/varbase_starter resolve and install on a Drupal CMS project at Composer's default minimum-stability: stable. Every dependency it needs is now released; this template was the last thing still pointing at dev branches.

Changes

• composer.json: version 1.0.x-dev -> 1.0.1.
• composer.json: repin all 15 dev-pinned requirements to released constraints. A dev constraint can never resolve at stable stability.
  • 14 Varbase base recipes 1.0.x-dev -> ~1.0.0: varbase_admin_base, varbase_users_base, varbase_security_base, varbase_performance_base, varbase_media_base, varbase_editor_base, varbase_content_base, varbase_canvas_base, varbase_workflow_base, varbase_seo_base, varbase_webform_base, varbase_page_base, varbase_blog_base, varbase_demo_content.
  • drupal/vartheme_bs5 5.0.x-dev -> ~5.0.0 (released at 5.0.2).
• README.md: version badge -> 1.0.1.
• CHANGELOG.md: add the 1.0.1 entry and its compare links.

No other change.

Release notes

• Fix #3621334: Remove the four never-applied base recipes, so the template resolves on Stable for Drupal CMS.
• Task #3621399: Update @vardot/varbase-e2e to ^2.0.4.
• Fix #3621553: Temporarily remove Entity Clone functional testing coverage.
• Pin all base recipes and Vartheme BS5 to released versions (move from dev branches).

Checkpoints

• composer.json is valid JSON and carries zero dev constraints
• Every pinned version verified against a real tag on git.drupalcode.org and a published release node
• Tilde floor kept at the .0 of the minor (~1.0.0, ~5.0.0)
• Pipeline green
• Reviewed by a human
• Code review by maintainers

AI-Generated: Yes