Semi-automatic debloater

The current minimum storage requirements for Chunky is 23MiB* not including scene data. After downloading a few different releases, particularly snapshots, it is possible for the lib directory to exceed 100MiB (and in some cases exceed 170MiB or more). Furthermore a typical scene will export multiple snapshots at set intervals, default 500 SPP, which under the default export option of PNG alone can be ~2MB for a 1920x1080 render.

As such I am proposing, either natively within Chunky or via a plugin, a method to analyse the current storage usage and to offer a number of cleanup options.

---

`lib`

Core (/shared) libs are commons-math3, fastutil, and gson. Each version .jar is around ~2MB in size.

Cleanup option recommendations:

- All stable + Latest per release channel (ie 1.4.5, etc., , 2.4.3, 2.5.0-snapshot)
- Latest per release channel (2.4.3, (stable-snapshot), 2.5.0-snapshot)
- Latest Stable only (2.4.3)
- Remove PRs/dev builds

---

`scenes`

An example folder:

Of the 842MiB, 379MiB are `.pfm` files, 171MiB are for scene `.backup` files, 63.5MiB are standard dump related snapshots, and 49.8MiB are denoised snapshots.

Cleanup of `.backups` should not typically be performed as it's possible for `.dump` and `.json` files to be corrupted. Subject to removal *may* be `.pfm` located within the `scenes\` folder only (ie denoiser plugin cleanup). However main efforts should be focused on the `snapshots` folder.

- Purge `snapshots` folder
- Remove all except latest - must follow standard `-spp.*`, is not the highest SPP, but last modified. Unless we read the SPP from the scene `.json`. Should **NOT** removed any custom content with non-standard naming ie `test.*`.
- Remove `.backup`s - **NOT** recommended but can save space!

---