task: #3607841 Update Drupal core from ~11.3.0 to ~11.4.0 on the 2.0.x branch

Update the Drupal core constraint from ~11.3.0 to ~11.4.0 on the 2.0.x branch (used by Varbase 10.1.x) so it supports Drupal 11.4 (released 1 July 2026), and switch CI to a strict-gating drupalci pipeline with a webship-js (Playwright + Cucumber-js) BDD browser test.

Issue: https://www.drupal.org/i/3607841

What changed

• varbase_dashboards.info.yml: core_version_requirement: ~11.4.0.
• composer.json: drupal/core: ~11.4.0; added drupal/layout_builder_restrictions: ~3 (the default recipe installs it and the Dashboard contrib module uses its PluginHelperTrait); dropped the module-level allow-plugins block and vardot/varbase-patches (added by the CI composer job).
• .gitlab-ci.yml: strict-gating drupalci CI — DRUPAL_CORE: 11.4.0, IGNORE_PROJECT_DRUPAL_CORE_VERSION: 1, _ALL_VALIDATE_ALLOW_FAILURE: 0; every validate job (composer-lint, cspell, eslint, phpcs, phpstan, stylelint) is allow_failure: false; a webship-js-test job installs a Drupal Standard site + Varbase Dashboards and runs the tests/features/drupal/** BDD suite.
• Added .gitlab-ci-local.yml for running the same validation jobs locally with gitlab-ci-local.
• Adopted core-compatible minimal lint configs (.eslintrc.json, .stylelintrc.json, ignore files, .cspell.json) and webship-js test dependencies in package.json.
• Added the webship-js suite: tests/features/drupal/**, selectors, step definitions, cucumber.js, playwright.config.ts, and a tests/varbase_dashboards_test_setup recipe (creates the four Varbase roles + the varbase_simple_workflow workflow the default recipe/views depend on, which a full Varbase site provides).

Testing

Green MR pipeline: https://git.drupalcode.org/project/varbase_dashboards/-/pipelines/874144 — all 8 jobs pass with allow_failure: false (composer, composer-lint, cspell, eslint, phpcs, phpstan, stylelint, webship-js-test = 5 BDD scenarios / 18 steps).

AI-Generated: Yes (Claude Code)

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