test: #3610873 Add a Varbase functional testing suite for the Varbase Events Base recipe

Adds a Varbase functional testing suite (Playwright + Cucumber-js) for the Varbase Events Base recipe, the GitLab CI job that runs it, and a small recipe fix the tests caught.

What this does

• Adds a functional test suite covering:
  • the Event content type's fields on the add form
  • event authoring: create, edit, and adding a featured image from the media library
  • the events listing at /events — cards, the result summary, the exposed "Search by" and "Type" filters, and the pager
  • the Related events block on an event's page
  • editorial-role permissions (who can create/edit/delete an event)
• Adds a self-contained "🧪 Automated Functional Testing" GitLab CI job that builds a Varbase project, applies a Site-template recipe of Varbase Starter + Varbase Events Base, seeds the test users and a 15-event fixture, serves the site, and runs the suite.
• Fixes recipe.yml so the events listing actually renders: adds varbase_components to the recipe's install: list — the events listing view's exposed form uses that module's components_exposed_form plugin, which was not being installed.

Issue

Closes https://www.drupal.org/project/varbase_events_base/issues/3610873

AI-Generated: Yes (Used Claude Code to write the Varbase functional testing suite, the CI job, and the varbase_components recipe fix)

By: Natshah

Update

Branch now matches the flattened test suite + test-content recipe; the full suite passes locally via gitlab-ci-local (16 scenarios, 16 passed). .gitlab-ci.yml temporarily pins varbase_components to the issue-fork of #3611182 (MR !46) until that merges.

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