Add additional tests for Enketo Form functionality

[jkuester]

Describe the issue
During AT for #6345, there were a number of behavior issues that were found that were not covered by any sort of automated tests. It would be very beneficial to have automated tests for these cases before the next Enketo uplift in #7599.

• Submit a form with a non-relevant inputs group. Verify the data in the inputs group is still saved.
  • It would also be good to have at least one of the fields in the inputs group to have a constraint that is violated when saving the form. Verify that the form still saves properly since the inputs group is not relevant.
• Submit a form that uses data loaded from the patient's contact-summary (e.g. the default delivery form loads in the pregnancy UUID). Verify the contact summary data is properly loaded (e.g. that the pregnancy UUID is saved for the delivery report).
• Submit a form using the instance::db-doc and instance::db-doc-ref functionality and verify the new reports are properly created along with the expected doc-refs. (e.g. new contacts are created for the babies entered into the default delivery form.)
• Submit a form with a required tel field and verify this is properly handled by the phone-widget proper and the report is saved.
• Create a completely new test using the enketo widgets we don't have in our forms -> Example forms

[ngaruko]

Is this still valid @jkuester ? If yes, should we give send it to to do or backlog?

[jkuester]

@ngaruko yes it is still valid! (And would be really good to address before #7599.) I am not sure about the difference between to-do and backlog, though.... 😕

[ngaruko]

Thanks @jkuester .
I think @michaelkohn would like the To Do column have 'things that we are definitely going to work on in the immediate future given our current capacity'. So, maybe not in to do yet.

[michaelkohn]

Looks like this issue is in Allies Code Health, please work with @mrjones-plip to organize.

[tatilepizs]

Merged into master.
PR #8480