REF] Standardise validation of mapped fields in imports, fix over-zealous requirements when matching on trxn_id, invoice_id for update

[eileenmcnaughton]

Overview

[REF] Standardise validation of mapped fields in imports, fix excessive required fields when matching on trxn_id, invoice_id`

Before

Validattion is still happening in multiple places & each is a bit different

Importing contributions with 'update existing' + trxn_id unnecessarily requires create fields like total_amount & financial type

After

Single place which processes an and/or array - form starts to call the parser layer

Possible to import with trxn_id and do an update without all create fields

Technical Details

This has new test cover for the Contribution import, including the trxn_id situation described and substantial test cover in CRM_Contact_Import_Parser_ContactTest - in particular testValidation

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).

[eileenmcnaughton]

unrelated fail