feat: #3619860 Install the Config Language Lock module by default

Issue: #3619860 Install the Config Language Lock module by default

What this changes

• recipe.yml: adds config_language_lock to install:, after content_translation.
• composer.json: adds drupal/config_language_lock: ~1 to require.
• recipe.yml: adds a config_language_lock.settings config action before the existing language.content_settings.canvas_page.canvas_page action:

config_language_lock.settings:
  simple_config_update:
    locked_langcode: en
    follow_site_default: true

Why

On a multilingual site, simple configuration keeps picking up the active interface language instead of staying on one fixed langcode, which makes exported config differ per editor session. Config Language Lock pins it. follow_site_default: true keeps the lock aligned with the site default language rather than hardcoding en forever.

config_language_lock is at 1.0.1, a stable release.

Note on rebasing

#3619859 also touches the install: list in recipe.yml. Whichever of the two merges second will need a trivial rebase on that one list.

Upstream issue found while testing this

• config_language_lock#3613945, filed by us: follow_site_default is implemented only in two form submit handlers; getLockedLangcode() never reads it. So locked_langcode: en plus follow_site_default: true, exactly what this MR ships, is contradictory on any site whose default language is not English: the lock stays en until someone submits the language overview form, which then moves it to the site default and rewrites every configuration object (measured: 116 objects, 102 translations updated, 96 removed).

Practical consequence for this recipe: with Canvas installed, hook_runtime_requirements errors unless follow_site_default === true && locked_langcode === site default, so a Varbase site installed in a non-English language gets a red status report error out of the box from this configuration. Verified on an English default site that the check passes there (en === en).

Config Language Lock tracks its issues as GitLab work items rather than in the drupal.org issue queue, which is why that link differs in shape.

AI-Generated: Yes

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