Add unit test & handling for processing from UserJob configuration rather than form submitted values

[eileenmcnaughton]

Overview

Add unit test & handling for processing from UserJob configuration rather than form submitted values

Before

Processing of imports deeping tied to quickform form set up

After

Starting to move to support the configuration being saved into the UserJob table as two arrays

'import mappings' - which is the row by row information of what field each csv column maps to, and potentially other data
entity_configuration - this isn't covered in this PR but will hold the stuff that relates to the entity rather than the rows

Technical Details

The import flow only supports limited config at the moment because of quickform challenges - this starts to add the support for config-based imports - where the config is stored in the UserJob rather than being tightly tied to the form.

When the import cleanup started the config was passed around in a whole lot of crazy ways. It has been consolidated to the submitted_values array which is stored in the user job but the next step in the evolution is for the form layer to transform the config to a sensible format & save it like that rather than drive everything from what the form supports

Comments

[civibot]

(Standard links)

• If this is your first pull-request for CiviCRM, please browse CONTRIBUTING.md for information about the development and testing processes.
• If you are reviewing this pull-request, you may wish to consult the test sites and the Review Standards (long template, short template).

[colemanw]

Ok test cover looks good