Improve include/exclude rules

[SferaDev]

Originally excludeRules were properties that should be removed from the payload (ignored). While includeRules were REFERENCE properties that should be included into the payload.

With our current implementation we don't follow those definitions anymore, and we have overly simplified the concepts to a single MultiSelector.

The total options of the MultiSelector could be potentially calculated from the schema without any problem (this should avoid dataStore migrations too). So the excludeRules wouldn't be used anymore in the MultiSelector (as they never were the same concept as !includeRules).

However it would still be useful to allow deciding which optional properties (which can be default and or empty arrays) I want to remove from the payload. Maybe with another MultiSelector but not sure how.

Originally posted by @SferaDev in #336 (comment)