TechDebt: CSV Row Validation With Row State

[MacQSL]

Description of Changes

• Adds row-level validation the the CSVConfig
• Adds row level state for additional validation metadata
• Slightly modifies existing Critter CSV import to use the CSVRowState

Testing Notes

• Critter import should work as normal
• Check the Critter sex values are persisted (it now uses CSVRowState to store the uuid value for the sex_qualitative_option_id)

[github-actions]

Openshift URLs for the PR Deployment:

• App Route: https://biohubbc-app-1455-af2668-dev.apps.silver.devops.gov.bc.ca/
• Api Route: https://biohubbc-api-1455-af2668-dev.apps.silver.devops.gov.bc.ca/
• Pods: https://console.apps.silver.devops.gov.bc.ca/k8s/ns/af2668-dev/pods?name=1455

[codecov]

Codecov Report

Attention: Patch coverage is 72.72727% with 15 lines in your changes missing coverage. Please review.

Project coverage is 45.97%. Comparing base (fb14aa8) to head (f950919).
Report is 1 commits behind head on dev.

Files with missing lines	Patch %	Lines
api/src/utils/csv-utils/csv-config-validation.ts	68.88%	3 Missing and 11 partials ⚠️
...import-services/critter/import-critters-service.ts	0.00%	0 Missing and 1 partial ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##              dev    #1455      +/-   ##
==========================================
+ Coverage   45.93%   45.97%   +0.03%     
==========================================
  Files         910      910              
  Lines       23680    23698      +18     
  Branches     3488     3493       +5     
==========================================
+ Hits        10878    10895      +17     
+ Misses      12190    12189       -1     
- Partials      612      614       +2     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[NickPhura]

Not specifically related to this PR:

In the CSVError interface, it might be good to more explicitly define some of the fields. Mostly I was thinking of the header field, and was wondering if that was the user facing header, or the internal header. I would have assumed user facing header, since the error needs to make sense to the user. But wasn't sure if it could also be the internal header, and then is re-mapped before being sent to the frontend.