[Page updates] Pedestrian path to fix Google place routing

[anon33958190]

After various discussions on Discord over months, I made some changes to the pedestrian path, airport and places pages to document use of a routable pedestrian path to fix problems with external places. Specifically, I added problematic Google area place as a use case for routable paths, a link to routable path at the end of the airport page, and this subsection under the external providers section:

@Problems with external provider places

Some external provider search results cannot be linked to Waze places, either because they cannot be found in the external provider search tool, or because they cause save errors when linked. In addition, instant navigation using Waze’s automatic speech recognition only returns results from Google Maps and navigates users to their centers. If addition of real drivable roads can’t get users a correct route to a problematic external search result, a [[Pedestrian path#Routable pedestrian path|routable pedestrian path]] may be used. Due to its appearance, this is a fix of last resort for serious routing issues caused by external places.

Enough people have asked about it, and enough editors have successfully used it for years, so I figured it should be documented somewhere. Let me know what you think.