BDMS 350: water level csv feature test update

[jacob-a-brown]

Why

This PR addresses the following problem / context:

• measuring_person is the field staff that took the measurement, not a lexicon value

How

Implementation summary - the following was changed / added / removed:

• Removed measuring_person from the scenario Upload fails due to invalid lexicon values
• Added a scenario to test when measuring_person does not correspond with field_staff, field_staff_2, or field_staff_3

Notes

Any special considerations, workarounds, or follow-up work to note?

• Use bullet points here

[jacob-a-brown]

@jirhiker and @chasetmartin I made another minor update for review. Since it pertains to the feature file I added it to this PR:

In the summary I changed validation_errors_or_warnings to total_validation_errors_or_warnings because the summary just reports the total numbers, not the actual errors/warnings. Calling it validation_errors_or_warnings led to confusion since I was expecting it to list out those errors/warnings. Prepending total_ to the field name clarifies what the field communicates.

The actual errors/warnings are reported in the payload, the standard out, and the standard error.