<chromium> Leave a chance to all location providers to get a fix

In our case, the NetworkLocationProvider will always fail
for lack of a valid API token, and we don't want that to
take precedence over the QtPositioning-based backend.

Change-Id: Ic175bd3fb527a76a578ef3568f7ac7ed07c4ccad
Reviewed-by: Andras Becsi <andras.becsi@digia.com>
Reviewed-by: Zeno Albisser <zeno.albisser@digia.com>
<chromium> Disable location requests to the geolocation google API

If we don't have a valid token, it will fail anyway.
And for now we don't provide a way to use an existing API token.

Change-Id: I7208d5ebc9ba7350622686e208761950f26bdc63
Reviewed-by: Allan Sandfeld Jensen <allan.jensen@theqtcompany.com>
Reviewed-by: Andras Becsi <andras.becsi@digia.com>
Reviewed-by: Zeno Albisser <zeno.albisser@digia.com>