Add Google Maps Data Portability Connector

Owners expect "Google Maps" in Add source to mean a live Google-account authorization flow when Google exposes one. The current Google Maps work only imports owner-provided Timeline files, and presenting that as a Gmail-like connection would be dishonest.

The reference now has a Google Maps Timeline import connector for owner-provided files. That connector is useful, but it is not the source Tim asked for when he said "over api like Gmail." It cannot honestly be presented as a live Google Maps account connection.

The first-party Google Maps Data Portability connector SHALL use Google's Data Portability API for Maps resource groups documented by Google, SHALL NOT scrape Google Maps browser or mobile UI, and SHALL NOT emit Google Maps Timeline point/segment streams unless Google documents equivalent Data Portability resources.

The reference implementation SHALL treat each Google Maps Data Portability owner authorization as a connection-scoped provider authorization. It SHALL NOT reuse Gmail static-secret credentials, Google app passwords, or deployment-level OAuth client secrets as per-account source credentials.

The reference implementation SHALL implement Google Maps Data Portability through the shared provider-authorization setup lifecycle, encrypted credential store, run scheduler, and Collection Profile runtime seams rather than through source-specific console branches or per-account deployment environment variables.