Sometimes, old events can block workspace startup

[amisevsk]

Description

In some cases, an event (e.g. failure to mount a volume) can prevent a workspace from starting even if the event is older (e.g. referring to an old pod that is still terminating). It seems that DWO is too broad in searching for unrecoverable events, allowing events that apply to older pods to interfere with new ones.

How To Reproduce

No easy reproducer yet.

Expected behavior

We should make sure we're not including events that don't apply to the current workspace start during startup.

Additional context

Initially occurred while testing workspaces in Eclipse Che -- there was an issue with configmap from the Che routing reconciler that blocked workspace startup for a few minutes while old pods were terminated. Once the pods were gone, the workspace started normally.