Client state test harness for v2 UI

[micheal-w-wells]

Expanding on our return to tests now for v2:

npm run test from appv2:

• Mount and has store

• Tables - RecordSets on load #3171

• Map - RecordSetLayers on load #3172

• Activity on load #3173

• IAPP on load #3174

• Map - Layer Picker on load

  • Sane defaults on new visit
  • Remembers choices between visits
  • Loads WMS, KML, and drawn boundaries into state

• Tables - RecordSets on user change table #3175

• Map - RecordSetLayers on user change table #3176

• Activity on select

  • Activity loads, main map marker, main blob, photos, jurisdictions, suggested treatments, etc all update. Geo ready to update

• Activity on update

  • Local reflects remote (by taking what comes in 200), main map marker, main blob, jurisdictions, suggested treatments all update. New geo again ready to edit.

• Activity on delete

  • Main map marker, main activity state cleared, removed from local layers without refetching.

• IAPP on select

  • Loads related stuff, main map marker updates

• Map - WhatsHere - user draw whats here box

  • Use search shape to populate table
  • Search feature loaded for display
  • Can exit clean back to where we were

• Map - KML - user upload KML

• Tables - KML - user upload KML

• Map - Layer picker on change

• state, local storage, and maplibre updated (assert state and maplibre separately so we keep most of the tests portable)

Later: Batch, reports,