[bug]: Trigger must be deleted if underlying OAuth2 token credentials can't be refreshed

### Describe the bug

We receive large amount of ERROR log entries when trigger scheduler can not run workflow because underlying oAuth 2 connection is not valid at oAuth2 provider side (Google, SLACK, Office365...)

If we detect such issues we block/disable workflow BUT we have to remove scheduling instructions.

### Steps To Reproduce

We can not provide details for reproduction, the issue is caught in cloud environment.

### Expected behavior

- Trigger should be disabled
- If we block/disable due to internal errors it COULD BE FINE for end user to notify user about disablement

For me it would be nice to see that workflow disabled because oAuth has some specific visual detail that clearly tells the workflow owner that connection is problem.

NOTES for developer:
- catch invalid connection status - use listener on connection
- find deployments in environment connection belongs to
- it might be necessary to find projects referenced by deployment - projectDeployment, deploymentWorkflow, projectDeploymentWorkflowConnection
- find workflows which have SCHEDULER TRIGGER
- find workflow which uses invalid connection
- disable workflow deployment

### Version

0.24.3

### OS

linux

### Browser

chrome

### Additional context

_No response_