chore: bump minimum version of google-cloud-os-config and google-cloud-kms

[parthea]

Similar to #2582 to bump the minimum to versions that allow google-api-core 2.x

https://github.com/googleapis/python-kms/releases/tag/v2.4.1
https://github.com/googleapis/python-os-config/releases/tag/v1.3.1

root@6812609b122a:/# pip install google-cloud-kms==2.3.0 "google-api-core>=2"
Collecting google-cloud-kms==2.3.0
  Using cached google_cloud_kms-2.3.0-py2.py3-none-any.whl.metadata (4.0 kB)
Requirement already satisfied: google-api-core>=2 in ./venv/lib/python3.12/site-packages (2.30.0)
INFO: pip is looking at multiple versions of google-cloud-kms to determine which version is compatible with other requirements. This could take a while.
ERROR: Cannot install google-api-core>=2 and google-cloud-kms==2.3.0 because these package versions have conflicting dependencies.

The conflict is caused by:
    The user requested google-api-core>=2
    google-cloud-kms 2.3.0 depends on google-api-core<2.0.0dev and >=1.22.2

Additionally, some packages in these conflicts have no matching distributions available for your environment:
    google-api-core

To fix this you could try to:
1. loosen the range of package versions you've specified
2. remove package versions to allow pip to attempt to solve the dependency conflict

ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflicts

root@6812609b122a:/# pip install google-cloud-os-config==1.0.0 "google-api-core>=2"
Collecting google-cloud-os-config==1.0.0
  Downloading google_cloud_os_config-1.0.0-py2.py3-none-any.whl.metadata (3.9 kB)
Requirement already satisfied: google-api-core>=2 in ./venv/lib/python3.12/site-packages (2.30.0)
INFO: pip is looking at multiple versions of google-cloud-os-config to determine which version is compatible with other requirements. This could take a while.
ERROR: Cannot install google-api-core>=2 and google-cloud-os-config==1.0.0 because these package versions have conflicting dependencies.

The conflict is caused by:
    The user requested google-api-core>=2
    google-cloud-os-config 1.0.0 depends on google-api-core<2.0.0dev and >=1.22.0

Additionally, some packages in these conflicts have no matching distributions available for your environment:
    google-api-core

To fix this you could try to:
1. loosen the range of package versions you've specified
2. remove package versions to allow pip to attempt to solve the dependency conflict

ERROR: ResolutionImpossible: for help visit https://pip.pypa.io/en/latest/topics/dependency-resolution/#dealing-with-dependency-conflicts

[gemini-code-assist]

Summary of Changes

Hello, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request updates the minimum required versions for the google-cloud-kms and google-cloud-os-config client libraries. This change is crucial for ensuring that projects using these libraries can successfully integrate with google-api-core version 2.x, resolving previous dependency conflicts and improving overall library compatibility.

Highlights

• google-cloud-kms version bump: The minimum required version for google-cloud-kms has been updated from 2.3.0 to 2.4.1.
• google-cloud-os-config version bump: The minimum required version for google-cloud-os-config has been updated from 1.0.0 to 1.3.1.
• google-api-core compatibility: These version bumps resolve dependency conflicts, allowing compatibility with google-api-core versions 2.x and above.

Changelog

• gapic/templates/_pypi_packages.j2
  • Updated the lower_bound for google-cloud-kms to 2.4.1.
  • Updated the lower_bound for google-cloud-os-config to 1.3.1.

Activity

• No human activity has been recorded on this pull request yet.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request bumps the minimum required versions for google-cloud-kms to 2.4.1 and google-cloud-os-config to 1.3.1. These changes, made in the _pypi_packages.j2 template, are necessary to resolve dependency conflicts and enable support for google-api-core version 2.x. The update is correctly applied to the central template, ensuring that newly generated client libraries will have the correct dependency constraints. The change appears correct and follows the repository's conventions.

[chalmerlowe]

LGTM