Spicy version of the Map UI optimisaiton

[Arbyhisenaj]

Description

There's too many, but the main ones:

• Managing data now exists in settings (separate of managing and exploring contexts for users)
• Using a single sidebar with known as the navigator which uses tabs for the different data you can explore
• Members are listed in a table that is searchable
• Constituencies have a list column and selected content column
• Constituencies are searchable

issues remaining:

• I think the member list is only showing one source? need to check that it shows all the sources
• Need to adjust the 'vanishing point' for the Map as when the sidebar expands, the map doesn't adjust what's important.
• I'm not seeing the actual constituency data for some reason? I see it in the code but not in the browser. Not getting error messages in the console either.
• would be good show all constituencies instead of the ones just your members are in?
• Pinned feature
• Finessing the design to match figma

Motivation and Context

Optimising based on initial feedback from the onboarding process

How Can It Be Tested?

How Will This Be Deployed?

Screenshots (if appropriate):

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• I've checked the spec (e.g. Figma file) and documented any divergences.
• My code follows the code style of this project.
• My code follows the code style of this project.
• My change requires a change to the documentation.
• I've updated the documentation accordingly.
• Replace unused checkboxes with bullet points

[janbaykara]

Feel like this should be styled as rows divided by a border, rather than a series of cards.

[Arbyhisenaj]

Feel like this should be styled as rows divided by a border, rather than a series of cards.

Like this?

[janbaykara]

Somewhat inspired by the UI prototyping done here by @Arbyhisenaj and based on new requirements and roadmap plans, @GemCopeland and @ev-sc are working on an new iteration of the private mapping UI. So I propose we close this PR. Leave it to @joaquimds.