Move Temporary Content/Field Configurations to Varbase Content Base Recipe

Problem/Motivation

The Varbase Starter recipe currently includes a number of temporary modules and configuration items related to content, blocks, and storage fields. These were added early to unblock development, but keeping them in the Starter recipe makes it heavier, less focused, and harder to evolve.

As Varbase recipes mature, these configurations should live in more specialized service recipes instead of remaining in the Starter layer.

Proposed resolution

Move related config and required packages for Content, Block, storage fields to the Varbase Content Base recipe
#3570361: Initialize Varbase Content Base recipe for foundational content structure and management

Remaining tasks

• ✅ 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
• ✅ Code review from 1 Varbase core team member
• ✅ Full testing and approval
• ✅ Credit contributors
• ✅ Review with the product owner
• ✅ Update Release Notes
• ❌ Release varbase-11.0.0-alpha1, varbase_starter-1.0.0-alpha1

User interface changes

• N/A

API changes

• N/A

Data model changes

• N/A

Release notes snippet

• chore: #3570372 Move Temporary Content/Field Configurations to Varbase Content Base Recipe