Redesign handling of Webform and Commerce Fields

Problem/Motivation

Currently VAP handles Webform And Commerce field values directly in the code of the Table class. This is partly a legacy from the 7.x version of the module. It is bloating the code and makes the code maintenance a very difficult task, since there are no tests written to handle those exceptions.

Proposed resolution

Start the discussion on the options to make VAP more maintainable, while keeping the support for Webform and Commerce fields, since they are widely used.

Remaining tasks

Draft, discuss and decide on the options and next tasks.