feat: setup MapAndLabel with React Context and schema input fields per map feature

[jessicamcinchak]

A few key changes:

• Rebases to the latest @opensystemslab/map pre-release so we can drawMany
• Adds the concept of a "Schema" to the Editor modal, with an initial option for "Trees" (very similar to List)
• Displays a form reflecting the schema fields for each feature plotted on the map; "resetting" the map also removes the forms
  • Each form is rendered in a MUI Vertical Tabs panel (docs) - still a bit of polishing needed to match latest Figmas!
• Refactors the main component to use React Context (docs)
  • This had big benefits for reducing validation complexity and prop drilling with the List component, and we'll have similar layers of complexity to manage here
  • To start, I copied a lot directly from the List - this gets us to a play-with-able thing quick, but we'll definitely want to reduce duplication and extract some logic (especially around "Fields" I think) going forward - but this exercise should help us better understand which logic bits these components will share and what will need to be unique !

This component is feature-flagged and there's lots of known gaps/bugs/follow-ups to spin out of this, including and not limited to:

• Form validation & error handling
• handleSubmit - add form inputs to GeoJSON properties?
• Polish up designs to match Figma; can we highlight map features based on active tab?? (set color property on drawGeojsonData ??)
• Debug shifty map labels on modify

[github-actions]

Removed vultr server and associated DNS entries

[DafyddLlyr]

A few small comment / questions / fix-forwards. Solid groundwork here! 👍