Description

Added support for the textSearch API.

• Currently supports query, location, bounds, language, and region request parameters
• Added unit tests that give full coverage to the new logic added
• Updated the autoComplete example to make use of the new textSearch API for predictions that are query strings instead of concrete places, so we trigger a textSearch instead of getDetails and can display markers for all the results
• Added TODO for fast-follow task to extend support for our migration LatLngBounds class

Here is a gif of the autoComplete example showcasing choosing a specific place (which does a getDetails) vs. choosing a query string (which uses the new textSearch)

Testing

Built/ran unit tests and verified they all pass. Ran autoComplete example and verified it now does a textSearch request for query string predictions.