Save Database With Options to prune settings #5438
Description
Right now, bvt_settings serializes resource settings into the database and there's no option to strip those during saving. Much like the save with options supports removing snapshots, undo history, and original path, there should also be a setting to let the user exclude all settings from saving.
This may result in inconsistent analysis and so we might want to warn the user in the dialog, but we need to give them the option as it's always possible for future or current settings to have some identifiable information (such as PDB servers, python versions, etc) to end up in the resource scope and be saved into a database.