Add Google oauth2 token detector

[rgmz]

Description:

Google OAuth2 access tokens are (relatively) short-lived tokens that begin with ya29.. It is still necessary to detect oauth2 client_id/client_secret and refresh tokens.

Example: https://github.com/hashicorp/vault/blob/066b4a18088df8eac5bcabde4c2baa4dce44a0c6/website/content/docs/secrets/gcp.mdx#L259

./trufflehog filesystem ~/.npmrc
🐷🔑🐷  TruffleHog. Unearth your secrets. 🐷🔑🐷

2024-01-07T16:07:37-05:00	info-0	trufflehog	running source	{"source_manager_worker_id": "7iO7p", "with_units": true}
Found verified result 🐷🔑
Detector Type: GoogleOauth2
Decoder Type: PLAIN
Raw result: ya29.xxx
Expires_at: 2024-01-07 16:26:56 -0500 EST
Google_email: me@gmail.com
Email_verified: true
Scope: https://www.googleapis.com/auth/accounts.reauth https://www.googleapis.com/auth/appengine.admin https://www.googleapis.com/auth/cloud-platform https://www.googleapis.com/auth/compute https://www.googleapis.com/auth/sqlservice.login https://www.googleapis.com/auth/userinfo.email openid
Access_type: offline
File: /home/user/.npmrc
Line: 3

This is auxiliary to #2264.

Checklist:

• Tests passing (make test-community)?
• Lint passing (make lint this requires golangci-lint)?

[rosecodym]

This looks great, thanks for doing it! I have a few small questions.

[rgmz]

Done!

[rosecodym]

This looks great, thanks! I'm curious about testing this - did you have to generate a new access token each time you wanted run the tests? (Because they're so short-lived?)

[rgmz]

This looks great, thanks! I'm curious about testing this - did you have to generate a new access token each time you wanted run the tests? (Because they're so short-lived?)

Mostly yes. I generated my tokens by following this tutorial, because npm run artifactregistry-login will magically add new tokens to your .npmrc file.

https://cloud.google.com/artifact-registry/docs/nodejs/store-nodejs#gcloud

[dustin-decker]

Thank you!