Stop installing the deprecated Content Lock Timeout module

Problem/Motivation

Content Lock 3 merged Content Lock Timeout into Content Lock, and the old module is now lifecycle: deprecated. The recipe still installs it and ships config/content_lock_timeout.settings.yml, which nothing reads any more.

Nothing is broken here: recipe.yml already sets content_lock.settings:timeout to 1800, so stale locks expire. This is a cleanup.

Related: Varbase Core 9.2.x and 10.1.x lost the timeout entirely, see #3637144.

Steps to reproduce

1. Apply the recipe on Drupal 11.4.
2. Content Lock Timeout is enabled, and Drupal lists it as deprecated.

Proposed resolution

• Remove content_lock_timeout from the install: list in recipe.yml.
• Delete config/content_lock_timeout.settings.yml.
• Keep the content_lock.settings timeout simpleConfigUpdate.
• Add an Unreleased entry to CHANGELOG.md.

Follow-up, not in this issue: the Varbase profile 11.0.x still ships config/optional/ultimate_cron.job.content_lock_timeout_cron.yml.

Remaining tasks

• ✅ 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 varbase_content_base-1.0.6

User interface changes

• N/A

API changes

• N/A

Data model changes

• The recipe no longer installs Content Lock Timeout or its settings. Sites that already applied it keep them.

Release notes snippet

• The recipe no longer installs the deprecated Content Lock Timeout module.