Cannot properly catch pod events on OpenShift 4.10/4.11/4.12

[AObuchow]

Description

This is a followup to Workspace pod FailedScheduling event not being properly caught, which was addressed by catching the unschedulable condition. However, other failure events that DWO tries to catch may still not be properly detected if their event.count is set to 0 and never incremented (which seems to occur on OpenShift 4.10/4.11/4.12).

In order to address this, we should either:

• change the event occurrence thresholds that are 1 to 0
• or, create a function for determining the event count using both the new event.series.count API and old event.count API:

if event.series != nil {
	return event.series.count
} else if event.count > 0 {
	return event.count
} 
return 1

Either fix unfortunately won't help for the FailedMount event, which has a threshold of 3, but it's better than nothing.

Additional context

The upstream OpenShift bug regarding event.count and event.series.count not being set: https://issues.redhat.com/browse/OCPBUGS-3796