versioning and save on data modelling

Describe the feature you'd like to request

While having a save feature would help users in saving a data modelling. Having a versioning would enable users in reverting back to a specific version of schema if their model doesn't fulfill a certain user case.

Describe your use case and how the feature would improve your experience.

When working with use case the data would need to modified and worked on with various data models. For example:
if we work on a schema that has over 10 models. working on modifying them can take time, we can then save and come back to the model when needed. once deployed if the schema doesnt fulfill the use case. we will need to undo the changes and work on different strategy.
version would just enable users in just going back to a certain version and redoploy the schema.

Describe alternatives you've considered

manually save the schema or pull the changes and use git to maintain a version

Additional context

save + versioning that has maybe save upto 15 saves like IAM policy changes.

The issue names no files, tests, or entry points. Start by locating the data-modelling workflow and existing schema deployment handling; clarify the save limit, version restoration behavior, and redeployment acceptance criteria with maintainers.