feat: #3611408 Back to DEV

Related issue: https://www.drupal.org/project/varbase_project/issues/3611408

Back to DEV after releasing varbase_project 10.1.2:

• composer.json version: 10.1.2 → 10.1.x-dev
• composer.lock and patches.lock.json removed — release-only artifacts, regenerated fresh for each release
• vardot/varbase / vardot/varbase-patches constraints stay at ~10.1.0

Known CI consequence on this lock-less state: the build: composer job is expected to fail here. Without a lock, a fresh composer install resolves drupal/ckeditor_media_resize before the drupal-lenient plugin activates, landing on 1.0.0 instead of 1.1.0, and the 2026-07-16 patch (written for 1.1.0, added this release for the Social API / CKEditor Media Resize fixes) then fails to apply. Confirmed reproducible (2/2 fresh-install failures, not a flake — retrying the job does not help). This will resolve itself once the next release re-locks the branch; flagging so it isn't mistaken for a regression from this MR's actual diff.

AI-Generated: Yes (Back to DEV version bump drafted by the varbase-10-1-x-release agent; 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