Refactor Column data-mapping and configuration

[sstok]

Q	A
Bug Fix?	no
New Feature?	yes
BC Breaks?	yes
Deprecations?	no
Fixed Tickets

To newcomers it's very unclear how data-mapping actually works, and it's over complicated.
So instead the data-providing part is moved to the column itself, where the developer sets a callable to to extract the data from the data for the row.

And to improve DX, when no data_provider is configured the system tries to build one itself (Uses column-name, checks for array-access, property access and getter as last).

Further:

• Binding data is removed as this has never really worked as expected;
• Event listeners are removed from columns, only used for binding;
• Columns are no longer aware of the Datagrid (to reduce the circular dependency) (views are still aware of the of the DatagridView);
• Auto configuration of column (only when the option was not set)
  • Data-provider: Use column-name, check for array-access, property access, getter
    • Check if option was empty, and use all public data for compound;
    • Check if option was empty, and use column-name as key for "TextType";
  • Label: Humanize column-name

These changes make the column easier to use, and removes some YAGNI 👍

[sstok]

I decided to keep the DataTransformers (for now).