Closes #510
Closes #526

There are a couple of bugs involved in the latest release of Google Maps, both issues (#510 and #526) were caused by the version 3.32 which is experimental. Quoting Google:

The experimental version — currently 3.32 — contains the latest features and bug fixes as they are made publicly available. Changes made to the experimental version are not guaranteed to be feature stable. We encourage you to regularly test your applications with the experimental version, which you can do by adding v=3.32 when loading the API

We would like our default version to be the latest release version, and not the latest experimental version. To do so we set up v=3 if no version is specified by the user. Which will be, today 3/10/2018, 3.31:

The current release version is 3.31. You can request it with either of the following bootstraps:

<script async defer
    src="https://maps.googleapis.com/maps/api/js?v=3
        &key=YOUR_API_KEY&callback=initMap">

<script async defer
    src="https://maps.googleapis.com/maps/api/js?v=3.31
        &key=YOUR_API_KEY&callback=initMap">

I am going to use 3.31 to make sure that this library works, when 3.32 is released, we would need to check if the issues that are affecting us now, will still be affecting us then. But for now, I think this is a good solution, this is also recommended by Google:

In order to make sure that there are no issues arising from version rollover, we recommend that you explicitly specify the number of the current release version of the API in the bootstrap. For example, v=3.31.

Source: https://developers.google.com/maps/documentation/javascript/versions