WidgetConfiguration and RelationManagerConfiguration

[bendbot]

Why are WidgetConfiguration and RelationManagerConfiguration used when defining widgets and relationship managers?
This does not allow these components to be normally configured locally, via the fluent interface, as is done in other components. Yes, there is a $properties array, but it will not override the values of the standard properties, since they are protected. Because of this, you need to create separate classes or add conditions for the passed $properties. I would like to reuse these components in different places, and not jump between classes.
There is no autocompletion, you need to go to the class to find out what properties the class has to pass to $properties.

Simple examples

• different numbers of perPage elements in different places.
• different headings heading in different places.
  ...

I think it would be good to unify the behavior of Widget and RelationManager.