Adjust UI for the Field protection create/edit screen

Overview: "Data Import field protection screen needs some revised UI requirements to ensure that control fields do not require indicators or subfields, and some control fields are disallowed from protection. These UI changes accompany BE changes documented on MODDICORE-200. Additional logic updates will be added during Lotus development.

As a staff person working with Data Import and MARC records
I want to be able to set field protections without accidentally protecting key control fields
So that I do not create problems with Imports that update SRS MARC and their corresponding Inventory records

Scenarios

1. Scenario 1
   • Given the Settings/Data import/Field mapping Create/Edit screen
   • When a user enters any of these values in the Field field: Leader, LDR, 001, 002, 003, 004, 005, 009
   • Then disallow it and display a red error message below the field: Please enter * or other numeric value
   • NOTE: This is just a slight change to the current error wording
   • NOTE: If user leaves it blank but fills in any other fields (Ind1, Ind2, Subfield, Data), standard Stripes component messaging will appear
2. Scenario 2
   • Given the Settings/Data import/Field mapping Create/Edit screen
   • When a user enters any of these values in the Field field: 006, 007, 008
   • Then grey out the Ind 1, Ind 2, and Subfield fields so that no data can be entered into them
   • And disallow wildcard (asterisk) in the Data field
     • Display error message under Data field in red: Please enter other data
     • NOTE: Existing error message under Data field is fine for all other scenarios except this one
3. Scenario 3 (already implemented)
   • Given the Settings/Data import/Field mapping Create/Edit screen
   • When a user enters any of these values in the Field field: 010 through 998
   • Then require single characters in Ind 1, Ind 2, Subfield fields (including wildcards)
   • And allow longer data or wildcard (asterisk) in the Data field
   • NOTE: Existing error messages below Ind 1, Ind 2, Subfield, Data are fine; no adjustments needed
4. Scenario 4
   • Given the Settings/Data import/Field mapping Create/Edit screen
   • When a user enters the value 999 in the Field field
   • And f in the Ind 1 and/or Ind 2 fields
   • Then display a red error message below the Ind 1 and/or Ind 2 field: Please enter other value
   • NOTE: Current error message for Ind 1/Ind 2 = [space] is fine; we just need a refinement if they try to enter "f"
5. Scenario 5
   • Given the Settings/Data import/Field mapping Create/Edit screen
   • When a user enters the value 999 in the Field field
   • And * in the Ind 1 and Ind 2 fields
   • Then display a red error message below the Ind 1 and Ind 2 field: Please enter other value
   • NOTE: Current error message for Ind 1/Ind 2 = [space] is fine; we just need a refinement if they try to enter "*" for both indicator fields
6. Scenario 6
   • Ensure this story passes Accessibility testing
7. Scenario 7
   • Ensure automated testing coverage for this new code is 80% plus and confirm with screenshot