Members map [MEEP-140]

[janbaykara]

An MVP for displaying imported member data on a map.

(This PR inherits code from @Arbyhisenaj's work in #19 and merges it into the #24 branch in order to build off the API advances there.)

Description

Features

• Create, edit and delete map reports
• Add data sources as layers to map reports
• Manual data import button for data sources, which now geo-codes data for use in mapping
• Some fixes for the data source creation workflow

Codebase

• Adds NextJS route groups to manage different layout variants.
• Adds authenticated GraphiQL route for easier debugging

How Can It Be Tested?

Click 'reports' in the header, then create a report and add a data source that has some postcode data. You should see the pins on the map.

You can also run python manage.py test hub.tests.test_sources to verify tests are running correctly.

Screenshots (if appropriate):

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)

Checklist:

• I've checked the spec (e.g. Figma file) and documented any divergences.
• My code follows the code style of this project.

[linear]

MEEP-140 Level 2 - Ellen, TJ and Hope ask: where are my members?

[render]

Your Render PR Server URL is https://meep-intelligence-hub-frontend-pr-25.onrender.com.

Follow its progress at https://dashboard.render.com/web/srv-cnpk9nf79t8c73dt9ktg.

[conatus]

Assuming that the real action here begins with 8207ede and going from here.

[conatus]

I think this is safe enough to try, from a code review level. Builds on other bits, which I have reviewed in detail.

Balancing reviewing a really large pull request with the fact that sometimes at this stage in work, pull requests are large. Can we try and keep them a little smaller from here on in, ha.