Remove condition plugins from configuration if they match default configuration

Problem/Motivation

When using visibility rules for components we have the problem that the list of visibility rules is super long and that can be easily improved by checking all of the condition plugins and remove them from form state if they are the same as the default configuration.

I found that technique in core's ConditionPluginCollection. Maybe we should try to refactor the visibility settings at some point to make use of that plugin collection as well.

Steps to reproduce

1. Set a visibility rule for a component
2. Export config
3. See that many unused settings are saved as well

Proposed resolution

Check configuration state during form validation to remove values from form values.

Data model changes

Unnecessary visibility settings are no longer visible in config export.