Need to be able to nest match profiles under action profiles (Lotus)

Overview: A user will often need to use the same match profile, or the same action profile within the overall structure of a job profile, but FOLIO does not currently allow that. Two possible options laid out below.

Current workaround: Import the same file multiple times, associating different matches and actions to it each time.

Steps to Reproduce:

1. Log into FOLIO-snapshot as diku_admin
2. Go to Settings/Data Import and create the following profiles
3. Match profile 1
   • Incoming record: MARC Bib
   • Existing record: Instance
   • Field 001 (no indicators or subfield)
   • Exact match
   • Instance HRID
4. Match profile 2
   • Incoming record: Static match
   • Existing record: Holdings
   • Text "Online (E)"
   • Exact match
   • Holdings Permanent Location
5. Action 1
   • Name: Update Instance
   • Action: Update
   • FOLIO record type: Instance
6. Action 2
   • Name: Update Holdings
   • Action: Update
   • FOLIO record type: Holdings
7. Field mapping 1
   • Name: Field mapping 1
   • Incoming record type: MARC Bib
   • FOLIO record type: Instance
   • Suppress from discovery: Mark for all affected records
   • Link to Action profile 1 (Update instance)
8. Field mapping 2
   • Name: Field mapping 2
   • Incoming record type: MARC Bib
   • FOLIO record type: Holdings
   • Suppress from discovery: Mark for all affected records
   • Link to Action profile 2 (Update holdings)
9. Create a job profile that matches on HRID and updates the Instance, then sub-matches on Holdings Permanent location and updates the Holdings

Expected Results: What should happen
I should be able to create a job profile like this:

• Match profile 1
  • Action profile 1
• Match profile 1
  • Match profile 2
    • Action profile 2

Or ideally a job like this (except matches cannot be nested after actions right now)

• Match profile 1
  • Action profile 1
  • Match profile 2
    • Action profile 2

Actual Results: Cannot create a job profile that lists the same match twice in the hierarchy and has different actions under each one

Additional Information: See attached video or screenshot

KS: the second scenario is preferable, does not need any BE work