Moving to Test Framework (component for OCP tests/ CI jobs) as discussed via Slack

Fabio could you carry this fix forward to the target release this was cloned for?

@Devan, which fix do you mean?

This ticket is about allowing single-node upgrade e2e jobs to tolerate operators going unavailable.

Fabio sorry we thought this was a clone to have a fix backported.

Do you have anyone planning to look at this change?

@Devan, no problem, thanks for the reply.

We aren't not planning to look into this change. We created this ticket and assigned it to Test Infrastructure team hoping someone more familiar with CI would adjust the single-node upgrade jobs to tolerate operators going Available=false. Apparently it was agreed on Slack that this ticket belongs to Test Framework team.

Just to give you more context, in the description of this ticket there's an explanation of why I think Available=false operators is OK in SNO upgrade jobs. Specifically, IMO the following test is not useful in those jobs:

> should not change condition/Available 

I'm assigning the ticket back to you, but feel free to reassign it or close it if you folks don't agree with this change.