Temporarily remove Entity Clone until it has a stable release, to resolve on Stable for Drupal CMS

Problem/Motivation

drupal/entity_clone has no stable release. 2.x is beta only, so any project resolving with Composer's default minimum-stability: stable cannot install a recipe that requires it:

drupal/entity_clone ~2 -> found drupal/entity_clone[2.0.0-alpha1, ..., 2.2.0-beta1] but it does not match your minimum-stability.

That blocks the Varbase site templates from being installed on Drupal CMS, where a site template has to resolve on stable. Entity Clone is required by three Varbase base recipes, so it blocks all of them: this one, Varbase Admin Base and Varbase Content Base.

This recipe goes furthest with it: entity_clone is in the install: list and in config.import with '*', so all three references have to go.

Worth noting separately: entity cloning is not an SEO concern, so this recipe is arguably the wrong home for it. That is a placement question for another issue, not a reason to keep it here.

We asked the maintainers for a stable 2.x tag in #3189738.

This removal is temporary. When Entity Clone 2.x has a stable release, it goes back if this recipe needs it.

Steps to reproduce

1. On a project with the default minimum-stability: stable, run composer require drupal/varbase_seo_base:~1.0.0.
2. Resolution fails on drupal/entity_clone.

Proposed resolution

Remove all three references:

• drupal/entity_clone from composer.json
• entity_clone from the install: list in recipe.yml
• entity_clone: '*' from config.import in recipe.yml

Check for any shipped entity_clone.* config files in the recipe and remove those too.

Sites already running the module keep it enabled; Composer simply stops requiring it. Worth a release note so a site owner who wants entity cloning knows to require it themselves.

A longer-term option is a clone workflow built on ECA, which Varbase already ships: eca_content provides an Entity: clone existing action. It performs a shallow createDuplicate() and does not follow referenced entities or translations, so it needs prototyping before it could replace the module.

Remaining tasks

• ✅ File an issue
• ✅ Addition/Change/Update/Fix
• ✅ Testing to ensure no regression
• ✅ Reviewed by a human
• ✅ Code review by maintainers
• ✅ Release varbase_seo_base-1.0.1

User interface changes

• On a new site the Entity Clone tab and its clone action are no longer present, because the module is no longer installed by this recipe.

API changes

• drupal/entity_clone is no longer required by this recipe, and its configuration is no longer imported.

Data model changes

• None. Existing entity_clone configuration on an installed site is left as it is.

Release notes snippet

• Temporarily stop requiring, installing and configuring Entity Clone, which has no stable release, so the recipe resolves on a project with the default stable stability. It returns when #3189738 ships a stable 2.x.