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

Update the Drupal core constraint from ~11.3.0 to ~11.4.0 on the 10.1.x branch (used by Varbase 10.1.x) in composer.json and varbase_blog.info.yml so it supports Drupal 11.4 (released 1 July 2026).

This MR also adopts the drupalci strict-gating CI (every validation job allow_failure:false) and a webship-js (Playwright + Cucumber-js) BDD browser suite for the Blog post content type.

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

What changed

• .gitlab-ci.yml: drupalci strict-gating pipeline (DRUPAL_CORE 11.4.0, IGNORE_PROJECT_DRUPAL_CORE_VERSION, _ALL_VALIDATE_ALLOW_FAILURE 0; per-job allow_failure:false on composer-lint/cspell/eslint/phpcs/phpstan; vardot/varbase-patches ~10.1.0; symfony/runtime allow-plugin). Added .gitlab-ci-local.yml.
• Core-compatible lint configs (.eslintrc.json, .eslintignore, .stylelintrc.json, .stylelintignore, trimmed .cspell.json) and webship-js deps in package.json.
• Added vardot/module-installer-factory and vardot/entity-definition-update-manager to composer.json (phpstan symbol resolution).
• webship-js suite: tests/features/drupal/** (login, content type, content, permissions), selectors, step definitions, cucumber.js, playwright.config.ts, and the slim tests/varbase_blog_test recipe that creates the Blog post content type on a Standard site.

Test results

Fully green strict-gating pipeline: https://git.drupalcode.org/project/varbase_blog/-/pipelines/874149 — 7/7 jobs success, all allow_failure:false (composer, composer-lint, cspell, eslint, phpcs, phpstan, webship-js-test). webship-js: 8 scenarios / 26 steps passed. No stylelint job (module ships no CSS).

Note: the webship job provisions the Blog post content type via a slim test recipe rather than cascading the full varbase_blog dependency stack, because the only sibling RELEASES on the Composer facade (varbase_editor 10.1.2, ckeditor_bidi 5.2.1, ...) carry config incompatible with current core/contrib schemas (fixes are only on the unreleased 10.1.x branches).

AI-Generated: Yes (prepared with Claude Code; 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