dataconnect(chore): move version defaults out of dataconnect.yml

[dconeybe]

Moves the default versions for Data Connect CI environments from the GitHub workflow YAML files into a dedicated shell script. The motivation for this change is to avoid triggering a large set of irrelevant GitHub actions when these versions change.

Highlights

• Created fill_ci_defaults.sh to centralize the default versions used in Data Connect CI.
• Updated dataconnect.yml and dataconnect_demo_app.yml to load these defaults dynamically using the new script.
• Adjusted the significance level in AbstractWithEvenNumDigitsDistributionUnitTest to improve test reliability.

Changelog

View file-level changes

• dataconnect.yml: Removed hardcoded version defaults and added a step to load them from fill_ci_defaults.sh.
• dataconnect_demo_app.yml: Updated sparse-checkout to include the CI directory and added a step to load defaults.
• fill_ci_defaults.sh: Introduced a new script to define and export default CI versions.
• AbstractWithEvenNumDigitsDistributionUnitTest.kt: Updated Chi-Square test significance level from 0.0001 to 0.00001.

[gemini-code-assist]

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

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.

[github-actions]

📝 PRs merging into main branch

Our main branch should always be in a releasable state. If you are working on a larger change, or if you don't want this change to see the light of the day just yet, consider using a feature branch first, and only merge into the main branch when the code complete and ready to be released.