[Feature Request] Automated Versioning and Rollbacks for Compose Files

[AmIBeingObtuse]

Description

Is your feature request related to a problem? Please describe.
When making edits to compose files directly within the Arcane UI, it's easy to accidentally introduce a breaking change or a misconfiguration. Currently, reverting to the last known working setup requires relying on external version control or remembering to manually copy the YAML before making changes.

Describe the solution you'd like
I would like to see a built-in versioning system for compose.yaml files. The ideal workflow would include:

1. Automated Backups: Every time a compose file is updated and saved/deployed, Arcane automatically saves a snapshot of the previous state.
2. Easy Rollback: A UI element that allows users to quickly view, select, and restore a prior version of their configuration.
3. Configurable Retention: A setting (either globally or per-stack) to define how many previous versions to retain (e.g., keep the last 5 or 10 backups) to manage storage space efficiently.

Describe alternatives you've considered

• Manually copying and saving the YAML locally before applying any updates.
• Using external Git repositories, which can add unnecessary friction for quick, simple edits intended to be done right in the web UI.

Additional context
I have attached a mockup image demonstrating how this might look in the UI. It features a simple version history dropdown right inside the compose editor layout, making it intuitive to switch back to a previous working state.

Other

Trivia: Fun fact, I put this in the gethomepage homepage repo first. 🤦🤦😁😆 No idea why. gethomepage/homepage#6415