Fix cibuildwheel env

[Amar3tto]

Fixes #33253, Fixes #34990
Successful run: https://github.com/apache/beam/actions/runs/23949976584

Previous discussion: #37712

---

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

• Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
• Update CHANGES.md with noteworthy changes.
• If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.

[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 refactors the Python wheel building process by decoupling the cibuildwheel environment from the standard SDK virtual environment. By creating a dedicated virtual environment for cibuildwheel, the build process becomes more robust and avoids potential dependency conflicts during the wheel generation phase.

Highlights

• New Virtualenv Task: Introduced a dedicated 'setupCibuildwheelVirtualenv' task in the Gradle plugin to manage a separate virtual environment for cibuildwheel.
• Dependency Management: Updated the Python SDK build process to use the new cibuildwheel-specific virtual environment, ensuring cleaner dependency isolation.
• Build Configuration: Removed hardcoded cibuildwheel version logic from the build script, centralizing the installation within the new setup task.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

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.

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. ↩

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 56.82%. Comparing base (1ae923e) to head (803ed43).
⚠️ Report is 46 commits behind head on master.

Additional details and impacted files

@@             Coverage Diff              @@
##             master   #38066      +/-   ##
============================================
- Coverage     57.26%   56.82%   -0.45%     
+ Complexity     5115     3427    -1688     
============================================
  Files          1395     1179     -216     
  Lines        197818   188025    -9793     
  Branches       4817     3593    -1224     
============================================
- Hits         113275   106840    -6435     
+ Misses        80704    77793    -2911     
+ Partials       3839     3392     -447     

Flag	Coverage Δ
java	71.93% <ø> (+1.04%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.