ci: #3611860 Remove the temporary Varbase Components issue-fork pin from the functional testing CI

Removes the temporary varbase_components issue-fork Composer pin from the 🧪 Automated Functional Testing job in .gitlab-ci.yml, now that it's no longer needed.

What / why

The events listing view uses the components_exposed_form views exposed-form plugin. When the Varbase Events Base functional testing CI job was added, that plugin was not yet in Varbase Components 4.0.x, so the job temporarily pinned drupal/varbase_components to the issue-fork branch of Varbase Components issue #3611182.

Varbase Components !46 (issue #3611182) is now merged into 4.0.x, so the plugin resolves from 4.0.x-dev again. This MR removes:

• The six-line TEMPORARY comment block and the repositories.varbase_components_fork VCS repository line.
• The pinned drupal/varbase_components:dev-3611182-components-exposed-form as 4.0.x-dev argument from the composer require retry loop.

Everything else in the job (the retry loops, Apache setup, yarn install libraries sync, chmod -R a+rX, the seckit/antibot/big_pipe uninstalls, the /events health-check and the cucumber invocation) is unchanged.

Issue: https://www.drupal.org/project/varbase_events_base/issues/3611860

Note: the pipeline on this MR re-resolves varbase_components from 4.0.x-dev. If it fails only because drupal.org's dev dist packaging hasn't yet picked up the merged commit (the dist zip can lag the branch by a few hours), that's a packaging-lag issue, not a code issue — re-run the pipeline later.

AI-Generated: Yes (Used Claude Code to identify that Varbase Components MR !46 / issue #3611182 merged, confirm no existing issue/MR already covered this, and remove the obsolete pin from .gitlab-ci.yml; reviewed by Rajab Natshah.)

Checkpoints

• File an issue about this project
• Addition/Change/Update/Fix to this project
• Testing to ensure no regression
• Automated unit/functional testing coverage
• Developer Documentation support on feature change/addition
• User Guide Documentation support on feature change/addition
• UX/UI designer responsibilities
• Accessibility and Readability
• Reviewed by a human
• Code review by maintainers
• Full testing and approval
• Credit contributors
• Review with the product owner
• Update Release Notes
• Release