Refactor Map component

[laudickson]

The Map component is still in its infancy and needs some serious thought and buy-in from active developers as to what the component contract should be.

Some initial thoughts:

• There should just be 1 map component in the entire app, and developers who would like to work on map-related things should be using the 1 component
• That being said, the map component should be flexible enough and have enough prop support to be used for various applications

The assignee of this particular ticket should get a discussion going before writing any code, gain consensus for component contract, and then pop a PR with agreed-upon implementation

This is not a set-in-stone sort of implementation either, as this app grows and evolves, additional prop support should be carefully added in with consideration

Some suggestions for prop contract:

Interface MapProps:
{
  data: geojson;
  startingCoordinates: number[];
  mapStyle: string;
}