feat(datasource/docker): Add support for Google Application Default Credentials

[kvanzuijlen]

Changes

This PR adds support for Google Application Default Credentials, which also includes GKE Workload Identity. The benefit of using this is that you don't need a service account key (long-lived token) and is a well documented/best practice solution that doesn't need extra custom work on the end user side.

Context

As said in the section above, this PR alleviates the need for a long lived token and instead introduces an option to configure a well documented solution.

Documentation (please check one with an [x])

• I have updated the documentation, or
• No documentation update is required

How I've tested my work (please select one)

I have verified these changes via:

• Code inspection only, or
• Newly added/modified unit tests, or
• No unit tests but ran on a real repository, or
• Both unit tests + ran on a real repository

I'll run these changes on a real repository shortly!

[kvanzuijlen]

@viceice the code coverage (of course) fails. I don't know how much sense it makes to test my current changes but I can look into writing a test for it if desired. Let me know what you would like me to do!

[viceice]

please run on a real repo

[kvanzuijlen]

@viceice I ran it against a real repository and found out that I made a mistake. With the change I made the onboarding PR showed the expected PRs that it would create. Thus proofing (to me) that it works with Google Application Default Credentials, since I didn't set any authorization configs for Artifact Registry.

[kvanzuijlen]

@viceice Could you please re-review?

[rarkins]

Needs deconflicting

[kvanzuijlen]

@rarkins done

[viceice]

still broken pnpm lockfile

[kvanzuijlen]

@viceice Sorry about that, the pnpm lock file rebroke after I fixed it in my earlier commit. It's working now again and I also applied your PR feedback (should've checked it after applying my fixes). Thanks for taking the time to review my PR!

[kvanzuijlen]

@viceice is there something I need to change or can this feature be merged? Thank you for your time!

[rarkins]

@kvanzuijlen it's best that you don't merge from main any more because that resets the tests to require approval again

[kvanzuijlen]

@viceice I hadn't run prettier after the last PR suggestions, sorry about that.

[renovate-release]

🎉 This PR is included in version 36.102.0 🎉

The release is available on:

• GitHub release
• 36.102.0

Your semantic-release bot 📦🚀