fix(config): use exclusive for save types

[owlstronaut]

fixes #8195

There isn't anything warning users about combining different save types together, but they are mutually exclusive, and the last one wins. This adds exclusive to the definitions for the types that won't work together.

[wraithgar]

This needs to be done outside the context of argv parsing. Consider a user with multiple save declarations in their ini files, it's the same situation.

We have an exclusive attribute that we added for provenance to prevent users from doing --provenance and --provenance-file. I wonder if it is as easy as adding that attribute to each of these so they are exclusive w/ each other?

[owlstronaut]

This needs to be done outside the context of argv parsing. Consider a user with multiple save declarations in their ini files, it's the same situation.

We have an exclusive attribute that we added for provenance to prevent users from doing --provenance and --provenance-file. I wonder if it is as easy as adding that attribute to each of these so they are exclusive w/ each other?

@wraithgar

We can certainly do that! Are we okay that that will break anyone that has things currently using those together - depending on the bug behavior? I was trying to warn the user without a breaking change

[wraithgar]

Yes, if they're doing it now they're already broken but don't know it.