Ignore google-cloud-storage and google-api-client major version upgrade for dependabot

[cwperks]

Description

Creating this PR to reduce some noise from dependabot. Dependabot has been making PRs that upgrade google-cloud-storage from 1.x to 2.x which cannot be merged since additional code changes need to be made to adopt 2.x.

This PR mutes dependabot to prevent it from making any more PRs on a major version upgrade for this dependency in any of the modules under the /plugins folder.

Example PRs which will require additional changes:

• Bump com.google.cloud:google-cloud-storage from 1.113.1 to 2.43.0 in /plugins/repository-gcs #16043
• Bump com.google.api-client:google-api-client from 1.35.2 to 2.7.0 in /plugins/discovery-gce #15577
• Bump com.google.api-client:google-api-client from 1.35.2 to 2.6.0 in /plugins/discovery-gce #13938

You can find the syntax for dependabot.yml here: https://docs.github.com/en/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file

Check List

• Functionality includes testing.
• API changes companion pull request created, if applicable.
• Public documentation issue/PR created, if applicable.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

[sandeshkr419]

@cwperks - Are these major version upgrades breaking in nature?

If non-breaking, then instead of disabling the upgrades, we can just create up issues and someone can upgrade these dependencies.

If breaking, then we should identify & upgrade these dependencies only for main/3.0 and not backport them to 2.x.

In either scenario, disabling upgrades just to reduce noise doesn't seems like the ideal way to go ahead here. Also, I guess there is a command to tell dependabot to not upgrade certain package upgrades in PRs itself. Disabling them in code imply that we don't want to upgrade them at all - unless it gets identified by security vulnerabilities /CVEs.

Thoughts @dblock?

[dblock]

I am +1 on creating an issue on doing a major upgrade for these (and removing the change @cwperks added to prevent dependabot from doing the upgrade).

[cwperks]

Just got back from vacation. I will create an issue for tracking this and mention that these lines will need to be removed on upgrade.