Support for Places API (New)

[jz-notion]

Is your feature request related to a problem? Please describe.
Google Maps launched a new Places API along with updated pricing structure. The previous API is now marked as Places API (Legacy). This loader does not appear to support the new API & features.

• Migration guide: https://developers.google.com/maps/documentation/places/web-service/migrate-overview
• New pricing: https://mapsplatform.google.com/resources/blog/build-more-for-free-and-access-more-discounts-online-with-google-maps-platform-updates/

Describe the solution you'd like
Please add support for Places API (New).

Describe alternatives you've considered
Integrate with the new API directly.

[usefulthink]

There is nothing for us to do to support those new APIs, the classes used to interact with the new APIs share the places library in the Maps JavaScript API with their older counterparts.

As far as I know, the maps team is in the process of rebuilding the Places API Services and corresponding JS classes.
Since the older API and its classes (Geocoder, PlacesService, AutocompleteService, etc) are being relied upon a lot, they can't just change how those classes behave. They will likely just continue to talk to the old API endpoints. I would assume they will be deprecated at some point in the future.

The new API started off as just the REST API (iirc, the new Place class was published at the same time). New functionality is being added to this new set of APIs (for example the AutocompleteSuggestion class). Those new APIs will be talking to the newer REST APIs exclusively. But all of that is happening in the same google.maps.places namespace.