[Feature Request] Refining Application Deletion Process and Protecting docker-compose Configuration Files.

[azicen]

I recently migrated from TrueNAS to CasaOS, and I really like CasaOS. I appreciate its UI and the simplicity of its operations which still allow me to do most things well. It has reduced the mental burden of using NAS for me.

During my use these past few days, I've encountered two issues that I hope to discuss with you, and I hope you will consider my request.

1. The default check of Delete userdata when deleting container applications can easily lead to unintentional data loss for me. Without a "Recycle Bin", the deletion operation is dangerous and irreversible.
2. When an application created with the docker-compose command is deleted, the directory containing the yaml is also deleted.

Describe the solution you'd like

1. Do not default check Delete userdata when deleting applications.
2. After deleting the application, restore the directory where the yaml is stored, and do not delete the yaml used by the docker-compose command to create containers.

Describe alternatives you've considered

1. A "Recycle Bin" feature could be added to make the deletion process safer.
2. I've noticed that when using the docker-compose command to create container applications, CasaOS renames the original yaml to .bak and uses a more detailed yaml for container creation. Perhaps the new yaml could be stored in a different directory.

Additional context

OS: archlinux Version: v0.4.7