feat: enable "back" & "edit" navigation for List map fields and MapAndLabel using @opensystemslab/map v1.0.0-alpha.2

[jessicamcinchak]

A few key changes in here!

• Bumps @opensystemslab/map to v1.0.0-alpha.2
  • Fixes shifty labels when modifying features; now when you modify it should keep the same label
  • Enables processing a GeoJSON "FeatureCollection" passed into drawGeojsonData prop which is required for "back" navigation when drawMany is enabled (previously supported single "Feature")
• [List] Pre-populates drawing layer on the map when you click "Edit" for an existing item
  • Replaces feat[map-and-label]: repopulate list map when clicking back #3601
• [List] Fix bug preventing existing/pre-populated features from being successfully "cleared"
• [MapAndLabel] Updates handleSubmit to produce GeoJSON data
• [MapAndLabel] Pre-populates map drawing layer and tab fields when you come "back" or "change" from the Review page
• [MapAndLabel] Adds a very basic Review page summary
• [MapAndLabel] Fixes bug where no tabs were active when coming "back"/"changing" - always default to tab 0 as active

Testing:

• https://3612.planx.pizza/testing/works-to-trees-prototype (toggle on "TREES" feature flag first!)

Known bugs:

• [MapAndLabel] "Remove" button is still not hooked up, but introduction of drawGeojsonData here is precursor to being able to complete feat(map-and-label): Remove features #3595

[github-actions]

Removed vultr server and associated DNS entries

[jessicamcinchak]

[EPIC] Allow applicants to 'work to trees' to see and add more information about protected trees on a map

[jamdelion]

I'm getting this error when I try to view Map+Label cannot read properties of undefined (reading 'boundaryBBox' ):

I'm also not sure how developed this feature is yet, but I get a blank map on the list component:

[jessicamcinchak]

@jamdelion thanks for quickly catching both of these bugs !

• The boundaryBBox was an error on my side & we need to account for this occassionally being undefined in teams like "Testing" that don't have an obvious spatial boundary. When it is set, the zoom/pan on the map is more restricted
• The empty map & corresponding Unimplemented type 3 error thrown in the console is a weird one that can pop up related to failing to properly fetch OS Vector Tiles (see threads like this & this)
  • I can't recreate this locally or on staging/production (& no direct changes to OS Vector Tiles in this PR) - so hoping it's something specific to pizza domain headers set on requests or similar (recent instances of this error in #planx-errors seem to also confirm only pizza issue) - will double-check after merge and revert if necessary !
  • I've updated the List to use the satellite basemap in the meantime which is loading without issue, just the OS basemaps that are failing here !

[jamdelion]

@jamdelion thanks for quickly catching both of these bugs !

• The boundaryBBox was an error on my side & we need to account for this occassionally being undefined in teams like "Testing" that don't have an obvious spatial boundary. When it is set, the zoom/pan on the map is more restricted

• The empty map & corresponding Unimplemented type 3 error thrown in the console is a weird one that can pop up related to failing to properly fetch OS Vector Tiles (see threads like this & this)

  • I can't recreate this locally or on staging/production (& no direct changes to OS Vector Tiles in this PR) - so hoping it's something specific to pizza domain headers set on requests or similar (recent instances of this error in #planx-errors seem to also confirm only pizza issue) - will double-check after merge and revert if necessary !
  • I've updated the List to use the satellite basemap in the meantime which is loading without issue, just the OS basemaps that are failing here !

Nice, those are both fixed for me now. :)