Add daily test reporting

[emilypgoogle]

Adds daily test status to the Test Reporting bug. Unlike unit and instrumentation tests, all runs are always shown, since we currently only have 1 type of daily test.

Example output below.

---

Unit Tests

	#8009	#7983	#8002	#8027	#8028	#8025	Success Rate
firebase-dataconnect				✅		⛔	⛔ 50%

*+8 passing SDKs

Instrumentation Tests

All tests passing

Daily Tests

	Apr 15	Apr 16	Apr 17	Apr 18	Apr 19	Apr 20	Apr 21	Success Rate
AI Daily Tests	✅	✅	✅	✅	✅	✅	✅	✅ 100%

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

plugins test results

67 tests   67 ✅  1m 23s ⏱️
12 suites   0 💤
12 files     0 ❌

Results for commit 1d781ea.

♻️ This comment has been updated with latest results.

[rlazo]

/gemini review

[gemini-code-assist]

Code Review

This pull request introduces support for tracking and reporting daily AI tests. It updates the TestReport data model and enhances the TestReportGenerator to fetch daily workflow runs from the GitHub API and display them in a formatted Markdown table. Feedback focuses on fixing logic errors in the table generation—specifically addressing a data-header mismatch, potential division-by-zero errors, and fragile date calculations. It is also recommended to populate the report date from the API response and remove an unused import.