Functional testing fails: the path repository shadows released tags, so the varbase_ai_figma_base back-pin cannot resolve

Problem/Motivation

The functional-testing (Varbase) job has failed on every pipeline since 16 August 2026. The last green run on 1.0.x was 924431 on 15 August.

Composer cannot resolve:

- drupal/varbase_ai_figma_base 1.0.0-rc2 requires drupal/varbase_ai_figma ~1.0.0
  -> satisfiable by drupal/varbase_ai_figma[dev-1.0.x, 1.0.0-alpha1, ...] from composer repo
     but drupal/varbase_ai_figma[dev-<sha>] from path repo has higher repository priority.

The job installs the module under test from a Composer path repository (.gitlab-ci.yml, options: {"symlink": true}) with no declared version, so Composer supplies it as dev-<sha>. A path repository is canonical and outranks packages.drupal.org, so it shadows every released tag of this module.

drupal/varbase_ai_figma_base 1.0.0-rc2, tagged 16 August 2026, introduced a ~1.0.0 requirement pointing back at this module. A dev-<sha> package can never satisfy ~1.0.0, so the circular pin makes the job unresolvable.

Tagging a stable 1.0.0 does not fix this. The path repository would still shadow the new tag with dev-<sha>, so every future merge request on this project stays red. This is blocking the 1.0.0 release (#3621081).

Proposed resolution

Declare a version for the path repository so Composer can satisfy the back-pin, in both functional-testing job definitions:

composer config repositories.mut '{"type":"path","url":"'"$CI_PROJECT_DIR"'","options":{"symlink":true,"versions":{"drupal/varbase_ai_figma":"1.0.0"}}}'

The sibling varbase_ai_figma_base uses the same mut path-repository pattern but nothing pins back at it, which is why it never trips this.

Release notes snippet

• Fix the functional testing jobs, which could not resolve dependencies because the path repository shadowed released tags of this module.