[b/474913468, 479101966] CI/CD Optimization

[AmitJ98]

CI/CD Optimization: uv Adoption and Conditional Windows Workflows

This PR focuses on optimizing the CI/CD pipeline for speed, consistency, and resource efficiency.

Key Changes:

• 🎯 Targeted Workflow Execution:

  • Configured every workflow to run strictly based on the specific content type modified.

• ⚡ Fast Dependency Management (uv):

  • Migrated all package installation steps across both Linux and Windows workflows to use uv instead of standard pip.
  • This ensures faster setup times and consistent environment resolution across all CI jobs.

• 🪟 Optimized Windows Workflows:

  • Refactored windows_workflows.yml to include a changes job (using dorny/paths-filter).
  • Windows jobs (Tests, Validations, Builds) now run conditionally based on modified files.
    • Example: Touching a playbook will no longer trigger integration tests on Windows.
  • This aligns the Windows logic with the existing validations.yml structure, saving significant CI resources.

[gemini-code-assist]

Note

Gemini is unable to generate a summary for this pull request due to the file types involved not being currently supported.

[TalShafir1]

I have one main question:

Do we want to keep these in different files?
If so let's separate them to folders based on content type and then on contribution source

integrations/google
integrations/third_party
playbooks...
mp
tipcommon
...

If not (this is the plan we wanted to go with when more content types are added):
Let's have one mega flow that controls everything, and based on the PR's changed files it will know which other flows to run - tests, code checks, builds etc...

[TalShafir1]

I have one main question:

Do we want to keep these in different files? If so let's separate them to folders based on content type and then on contribution source

integrations/google integrations/third_party playbooks... mp tipcommon ...

If not (this is the plan we wanted to go with when more content types are added): Let's have one mega flow that controls everything, and based on the PR's changed files it will know which other flows to run - tests, code checks, builds etc...

This might will also help us determine what's required and what not. One single required to pass flow that knows which sub flows to run

[TalShafir1]

FYI Since some job names were changed they will not run here