INN-Reach Record Contribution Settings: Configure FOLIO Material Type to INN-Reach Central Item Type Mapping

Purpose:

User story statement(s):

As a FOLIO system administrator with appropriate permissions, I want to configure record contribution settings for each configured central server, including a mapping fo configured FOLIO material types to central INN-Reach item types.

Scenarios:

1. Scenario:
   1. Given the INN-Reach settings Record Contribution group (UIINREACH-18)
   2. When the user selects "Material type to item type mapping"
   3. Then a pane with a menu to select a configured central server is presented with an inactive "save & close" button
2. Scenario:
   1. Given the previous scenario
   2. When the user selects a central server
   3. Then a form with all of the configured FOLIO material types in a tabular list with a corresponding menu featuring the central server item types (retrieved via API call from the central server via mod-inn-reach API endpoint)
3. Scenario:
   1. Given the previous scenario
   2. When there is an existing mapping configuration for the selected central server
   3. Then it should be retrieved and used to populate the form, leaving any new material types unmapped and resetting the selection for any central item type that has been removed
4.  Scenario:
   1. Given the previous scenarios
   2. When the user has assigned a central item type for each FOLIO material type
   3. Then the "save & close" button becomes active
5. Scenario:
   1. Given the previous scenarios
   2. When the user attempts to navigate away from the form and modifications have been made but not saved
   3. Then as standard "are you sure?" modal is presented with "keep editing" and "close without saving" buttons
6. Scenario:
   1. Given the previous scenario
   2. When the user selects "keep editing"
   3. Then they are returned to the in-progress form
7. Scenario:
   1. Given scenario 5
   2. When the user selects "close without saving"
   3. Then the form is abandoned and not saved, and the user navigates to the requested screen
8. Scenario:
   1. Given the previous scenarios
   2. When the user activates an active "save & close" button
   3. Then the form is submitted to save the configuration
9. Scenario:
   1. Given the previous scenario
   2. When the form is valid and successfully saved
   3. Then a success toast is presented to the user indicating that the configuration has been created or updated successfully
10. Scenario:
    1. Given a form has been submitted
    2. When form cannot be saved
    3. Then an error toast is presented to the user providing a description of the error, the user is returned to the in-progress form, and any invalid form fields are indicated.