[CI] Disable fail-fast strategy for integration test jobs

[Torch3333]

Description

For integration tests in CI, we have two variants — default and group commit — for each storage integration test. If one of the variants fails, the other automatically fails without completing the tests. We disable this behavior so all integration tests can run to completion.

Related issues and/or PRs

• Support AlloyDB #3029 (comment)

Changes made

• Set fail-false to false in the matrix strategy for integration test jobs

Checklist

The following is a best-effort checklist. If any items in this checklist are not applicable to this PR or are dependent on other, unmerged PRs, please still mark the checkboxes after you have read and understood each item.

• I have commented my code, particularly in hard-to-understand areas.
• I have updated the documentation to reflect the changes.
• I have considered whether similar issues could occur in other products, components, or modules if this PR is for bug fixes.
• Any remaining open issues linked to this PR are documented and up-to-date (Jira, GitHub, etc.).
• Tests (unit, integration, etc.) have been added for the changes.
• My changes generate no new warnings.
• Any dependent changes in other PRs have been merged and published.

Additional notes (optional)

Provide any additional information or notes that may be relevant to the reviewers or stakeholders.

Release notes

N/A

[Copilot]

Pull Request Overview

This PR disables the fail-fast strategy for integration test jobs in the CI workflow to allow all test variants to run to completion even if one fails.

• Adds fail-fast: false to the matrix strategy configuration for all integration test jobs
• Ensures both default and group commit test variants run independently without early termination

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[komamitsu]

LGTM! 👍

[brfrn169]

LGTM! Thank you!