Component Config injection

[LastDragon-ru]

And get rid of arrays... Because it is extremely difficult to update examples in the docs when component settings were changed. There is also no validation for settings names, difficult to rename, difficult to deprecate, etc, etc. All of them can be solved if we will use objects instead of arrays.

Internally Laravel uses var_export to cache the config, so seems objects should be fine.

• Convert to objects
• Make sure that existing array based config still can be used (should trigger the deprecation message)
• Injection

[LastDragon-ru]

Make sure that existing array based config still can be used (should trigger the deprecation message)

Work for all except formatter (new config is too different)