Add toggles to MediaLibrary and disable default 'strip' functionality

[humantex]

Discussed in #3522

^{Originally posted by humantex August 17, 2022}
I'm considering using Fork for a new project, and I'm shocked that metadata stripping is hard coded and enabled by default without the ability to set it as an option in the backend with some kind of toggle.
 

As a photographer, artist, and content creator, I rely on the preservation of my copyright, usage limitations on licensing, publishing details in IPTC data, tag keywords, and so much more. Primarily stripping any/all data deprives me and other creatives of whatever legal protections the IPTC and EXIF data can provide us. Luckily I'm adept at writing/modifying code to remove the default stripping behaviour in config files, but most in my position may not have the same ability, and/or the funds to pay someone to change the code for them... that's assuming they're even aware it's happening at all, and they find out before it's too late.
 

Creatives producing their own media files - of all types, not just photos/images - understand whatever 'privacy' concerns there might be, and are active in monitoring, modifying, and most certainly adding more than the basic default values intentionally. We make a conscious effort to make sure the data is available and complete, and are well aware of what it means to have this embedded data exposed.
 

According to the documentation - at the corrected documentation link - the are no parameter options available within the strip function, and it can not trim fields or data types selectively. It's unfortunate that use of this library demands an all or nothing approach, but it's the one included with Fork, so...
 

Please allow ALL of us who rely on the data being left as-is on upload, with the capability to opt into the stripping of vital data, IF we choose to.