ci: add schedule reporter and cb failure reporter files

[kgala2]

Adds schedule reporter workflow action that runs daily to go through builds on Cloud Build and create/update failing tests issues

[jackwotherspoon]

This needs to be rebased I believe...

[jackwotherspoon]

@kgala2 What is the plan to test that this works?

[kgala2]

@kgala2 What is the plan to test that this works?

I will on purpose break one of the system tests to monitor this for 2 days

[jackwotherspoon]

I will on purpose break one of the system tests to monitor this for 2 days

@kgala2 Can you explain your thinking a little bit?

We do not want to push broken tests to our main branch...

An alternative solution off the top of my head would be to do the following:

• Add a placeholder to schedule_reporter.yml trigger names with something like manual-test-trigger
• Add a manual build trigger
• Add a test that asserts a failure to your test branch and manually trigger a build. Wait and see if the reporting tool picks it up and creates an issue on its next run.
• Put up a PR to remove the placeholder from schedule_reporter.yml once satisified

[jackwotherspoon]

On second thought, I guess you could do exactly what I said but with py-integration-test-nightly. You could just update the trigger to point at a test branch of yours with the simulated failure test and manually invoke the trigger. Then switch it back to point at main branch.

This would allow you to not need to use a placeholder trigger name.