wip: fix map web component loading bugs

[jessicamcinchak]

suspect that this is a challenge related to how Lit web components unmount/reload when integrated in React - guessing all bugs below will have same solution once we get to the bottom of it:

1. visual bug in FindProperty component related to back button behavior where previous OS Feature will still appear on map after searching a new address. Reload's correctly if you "restart application" rather than go-back. No passport implications, but visually confusing to user

• https://trello.com/c/6nVeR3jp/1619-about-the-property-map-returned-two-unrelated-polygons
• https://trello.com/c/YrIzKiXz/1569-super-zoomed-out-map-on-find-property
• https://trello.com/c/vMr17Jdy/1538-map-remembers-a-previously-searched-property

2. visual bug in DrawBoundary component related to back button behavior where two polygons are rendered on top of each other, but you can only modify one of them. Again, no passport implications (area & geojson are correctly calculated still), but visually confusing

• https://trello.com/c/CT5W8SVx/1609-fix-bug-where-clicking-back-makes-drawboundary-show-duplicate-boundaries
• current hacky fix fix: back button would create duplicate boundaries #696

3. DrawBoundary map fails to re-render with new props when radio button is toggled/state changes wip: click-to-select *or* draw a site boundary #688

maybe useful resources:

• https://www.brianperry.dev/posts/2021/working-around-reacts-web-component-limitations/
• https://www.npmjs.com/package/@lit-labs/react useController api

[jessicamcinchak]

closing in favor of #803 !