Automatically keep Input Data mappings and table columns in sync

[rob2universe]

Is your feature request related to a problem? Please describe.

DRD and table columns can get out of sync. It is an intuitive expectation that Input data in the DRD and the columns of the table they map to are kept in sync.
On the other hand and Input data should be added to the DRD if a column is created and the mapping (not the Input) should be removed if a column is removed.

Describe the solution you'd like

A table column should be created when an Input is mapped to a table in the DRD and removed when if the input mapping to the table is removed.

Describe alternatives you've considered

Manually maintain columns.

[nikku]

Thanks @rob2universe for opening this issue.

You'd not be surprised if the table is modified (side-effects) when deleting elements on the DRD?

I guess mapping shall work inversely, too (i.e. I add a column to a decision table and an input is being generated)? That would raise the question on whether inputs shall be mandatory on DRDs. You could of course say that "input modeling in DRD is optional", but once it is being done it shall always be representative of the actual decision table inputs.