Automatically create GitHub issue on failed upstream monitor CI

[Kircheneer]

Proposed Changes

The upstream monitor CI could automatically create issues when it fails.

Justification

This would save either the core team or the plugin maintainers from having to manually monitor the status of this CI part.

[glennmatthews]

Part of the issue at present is that the upstream monitor CI doesn't actually fail when tests fail; this was done to prevent failures in one App from causing the CI to be auto-canceled for the other Apps, but I think we can change how this is set up so that it actually reports failures when they occur.

[lampwins]

I would hate for this to turn into alert fatigue and basically become another dependabot for us. Like Glenn says, I think the right primary path here should be to truly integrate it into CI, instead of just opening issues across the ecosystem.

[Kircheneer]

I like this idea, too.