Configuration value "project" not set properly when using the configuration method 'OPTION 2' for Google

When passing in Google configuration information via 'OPTION 1', we manually set `"project": "your-project-name",`.

When using 'OPTION 3', `project` is set properly using either the environment variable:
`project: process.env.GOOGLE_PROJECT_ID,`
... or via the file pulled from `process.env.GOOGLE_APPLICATION_CREDENTIALS`:
`GoogleConfig.project = GoogleConfig.project_id;`

But when using 'OPTION 2' with a .json file downloaded from the Google control panel after creating the service account, `project_id` exists in the json but not `project`, so `GoogleConfig.project` never gets set.

This causes all the checks to appear as "UNKNOWN".

A workaround is to add the `project` item in the .json file, setting it to match the `project_id` node.

Start by tracing the configuration handling for Google 'OPTION 2' and compare how the downloaded service-account JSON maps project_id to project. Verify the fix with the existing Google checks or configuration tests, and consider it done when valid OPTION 2 credentials set project and checks no longer appear as UNKNOWN.

Written by the indexing model from the issue text.