Add a summary of the most often failing tests to the daily build report

[jonsimantov]

Description

Provide details of the change, and generalize the change in the PR title above.

Add a table of the failures/flakes that occur most often to the build summary.

---

Testing

Describe how you've tested these changes. Link any manually triggered Integration tests or CPP binary SDK Packaging Github Action workflows, if applicable.

Example: #1179 (unless it's been overridden)

---

Type of Change

Place an x the applicable box:

• Bug fix. Add the issue # below if applicable.
• New feature. A non-breaking change which adds functionality.
• Other, such as a build process or documentation change.

---

Notes

• Bug fixes and feature changes require an update to the Release Notes section of release_build_files/readme.md.
• Read the contribution guidelines CONTRIBUTING.md.
• Changes to the public API require an internal API review. If you'd like to help us make Firebase APIs better, please propose your change in a feature request so that we can discuss it together.

[github-actions]

Integration test with FLAKINESS (succeeded after retry)

Requested by @jonsimantov on commit 39c8aa6
Last updated: Fri Jun 16 02:35 PDT 2023
View integration test log & download artifacts

Failures	Configs
app_check	[TEST] [FLAKINESS] [Android] [1/3 os: windows] [1/2 android_device: android_target] (1 failed tests)   FirebaseAppCheckTest.TestDebugProviderValidToken
firestore	[TEST] [FLAKINESS] [Android] [2/3 os: macos windows] [1/2 android_device: android_target] (1 failed tests)   CRASH/TIMEOUT

Add flaky tests to go/fpl-cpp-flake-tracker