UI groundwork for report/map page

[Arbyhisenaj]

Description

• Correct the components.json file by chaging the basecolour back to slate (wasn't before becuase I though i could use a tailwind extended colour "meepGray-500"
• Added the UI for the map page using shadcn components mostly but also created custom components for the constituency items in the constituency data list
• Tried to set the color of the 'first and second in 2019' circles to be dynamic by using the party name as a prop in the styling e.g className=bg-${first2019lowercase} which might equal 'bg-labour' which is an extended colour we set in the tailwind config - but sometimes this doesn't seem to work, sometimes it does
• Added the rest of the fonts

Motivation and Context

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.

[conatus]

@Arbyhisenaj

Can you please fill out the remainder of the pull request template, especially the How Can It Be Tested? element. Thanks.

[conatus]

@janbaykara

Feels like we can close this PR out and merge this code in with #25, as feels it is implicitly reviewed by you using it in anger to build out the map for real.

Open again if you disagree.