task: #3637145 Stop installing the deprecated Content Lock Timeout module

Content Lock 3 merged Content Lock Timeout into Content Lock and deprecated it. The recipe already sets content_lock.settings:timeout to 1800, so this is a cleanup.

Issue: https://www.drupal.org/i/3637145 Related: https://www.drupal.org/i/3637144

• Remove content_lock_timeout from install: in recipe.yml.
• Delete config/content_lock_timeout.settings.yml.
• Add an Unreleased entry to CHANGELOG.md.

Local pipeline (gitlab-ci-local): composer-validate and yaml-lint green. Applying the recipe on plain Drupal installs Content Lock and no longer Content Lock Timeout. The opt-in "Install recipe site" job fails the same way on unchanged 1.0.x (Unable to determine class for field type 'yoast_seo'), so it is not this change.

Remaining

• Opt-in CI job: php vendor/bin/drush runs Drush's shell wrapper as PHP, and web/core/scripts/drupal recipe is gone on core 11.4. Separate issue.
• Follow-up: the Varbase profile 11.0.x still ships config/optional/ultimate_cron.job.content_lock_timeout_cron.yml.

AI-Generated: Yes

Checkpoints:

• File an issue
• Addition/Change/Update/Fix
• Testing to ensure no regression
• Automated unit testing coverage
• Automated functional testing coverage
• UX/UI designer responsibilities
• Readability
• Accessibility
• Performance
• Security
• Developer Documentation
• User Guide Documentation
• Reviewed by human
• Code review by maintainers
• Full testing and approval
• Credit contributors
• Review with the product owner
• Release notes snippet
• Release