A Robust Cleanup Option to Remove Old Versions and Records No Longer Needed to Optimize Storage and Usage

Concern:

Over time, the system keeps accumulating old versions and release records that are no longer required. These records are not used for deployments and have no business value anymore, yet they continue to consume storage and system resources.
Hence need a reliable and straightforward cleanup option that allows them to permanently remove obsolete data and keep the system optimized. Simply hiding records from the UI is not sufficient; the cleanup should actually free up storage.
Auditing is not a concern for these scenarios and should not prevent customers from cleaning up data that is no longer needed.

Customer Expectations:

Ability to clean up old, unused versions
Ability to remove obsolete releases
Real cleanup that frees storage
Better control over data growth and usage

Context

UCV currently imports all data from UCD, including snapshots and versions.
In UCD, snapshot/version cleanup is performed regularly.
Versions that are deleted in UCD continue to remain in UCV.
These versions are temporary in nature and are not used in any deployments or active releases.

Impact:

MongoDB continues to grow unnecessarily.
Approximately 3 GB of data growth within one year due to stale imported versions and releases.
Current archival functionality only hides releases from the UI and does not delete data from MongoDB.

Technical Requirement:

Provide a mechanism to permanently delete old imported versions when they are not referenced by any UCV release.
Provide a mechanism to permanently delete old releases from MongoDB, not just archive them.
Cleanup should be safe, controlled, and configurable, with auditing optional for non-production use cases.