Remove react-google-maps dependency

[Gnito]

react-google-maps library has been unmaintained for 3 years.

Google Maps integration will be operated without any react wrapper library from now on.
We just need a couple of classes from Google Maps API:

• OverlayView (This is needed to render HTML on top of the map.)
• Marker or
• "Circle" for fuzzy coordinates (I actually ended up using Polygon to improve roundness)

OverlayView is definitely the most complex setup. Luckily, part of the work to support it without react-google-maps was already done with some old bug fixes that were made on top of react-google-maps and generalization made to support Mapbox.

Other notes:

• Renaming: SearchMapWithGoogleMap => SearchMapWithGoogleMaps
• The default map provider is still Mapbox.

[kpuputti]

I will submit this partial review already now for you to read. I still have to review the largest file.

[kpuputti]

I think this is a bit too prone to conflict. If the id is really required, could it come as a prop from the page?

[Gnito]

I'd keep the id because Google Maps is quite difficult to debug without some document.getElementById() calls from DevTools. (The element on those map panes are not selectable by right-clicking on top of the map.)

Anyway, I passed the id ("searchMap") from SearchMap component, but I didn't push it further than that. (And anyway, it's unlikely that there's more than one SearchMap instance since it takes 2/5 of the entire screen.

[kpuputti]

Yes, it is unlikely that a page in the app will have multiple search maps. However, we do have plans to use the styleguide more for lots of things like map variants etc., so it would be helpful to be able to define unique IDs there.

[Gnito]

Showing these components, that take the entire-screen into use, needs some thinking. However, the change I made now should allow different ids to be passed for the SearchMap component.