feat: upload logs for catalyst workflows and extend timeout

[ncooke3]

• upload xcresult and build logs for catalyst CI testing
• extend timeout

Should provide more info on rarer Crashlytics flake: https://productionresultssa11.blob.core.windows.net/actions-results/02ec39f7-7972-4005-bdfe-9eb8b6e74ac3/workflow-job-run-58a11f9e-6250-546a-9ac6-ba502be8b6ee/logs/job/job-logs.txt?rsct=text%2Fplain&se=2026-01-05T16%3A53%3A54Z&sig=hlAUL9pmZlujpzYed3yu6DoYK1UY08JiGHKBy8Y6OoE%3D&ske=2026-01-06T04%3A15%3A30Z&skoid=ca7593d4-ee42-46cd-af88-8b886a2f84eb&sks=b&skt=2026-01-05T16%3A15%3A30Z&sktid=398a6654-997b-47e9-b12b-9515b896b4de&skv=2025-11-05&sp=r&spr=https&sr=b&st=2026-01-05T16%3A43%3A49Z&sv=2025-11-05

The fact that the context manager tests started twice implies a crash during a unit test. The crash report will be included in the xcresult bundle and should provide more info:

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

[ncooke3]

Failures are unrelated. Low hanging ones are addressed in #15666