Explore: Investigate what UI changes are needed for upgrading between 4.6 -> 4.10 Extended Update Support (EUS) releases

Goal
Work with console and ota teams to determine what UI changes we should consider for upgrading between 4.6 -> 4.10 Extended Update Support (EUS) releases.

Background
For background on this initiative, see

EUS to EUS Focus Area Discussion: https://docs.google.com/document/d/17I1Wd7-R1wRxmboyv1jUFHFkqQcBTorJccdGi1ZqjQE/edit?usp=sharing

EUS Feature: https://issues.redhat.com/browse/OCPPLAN-5484

• Is the EUS -> EUS upgrade user experience different than manually upgrading to each separate release?
• Should we show status differently in the UI during an EUS -> EUS upgrade?
• Do we need to show issues before/during upgrades beyond alerts
• Do we need a UI for overriding backpressure blocking an upgrade?

Some of the answers will depend on what API will be available. Under the hood, the EUS upgrade will be a set of serial upgrades through each version.

Is this where we consider using the modal that shows users the path to take based on where they are? (The mocks we made for OCM).

Acceptance Criteria

• Reach agreement in coordination with other teams on what UI changes are needed to support EUS -> EUS upgrades
• Understand what APIs will be available and whether there are any gaps for the desired user experience. (Currently we only look at the ClusterVersion APIs.)

Design Doc: https://docs.google.com/document/d/1iUZlHbv5nTYtb7Cq4rn_bYPqD4Jtie59xIogxN-2Eyc/edit#

Outcome - definition of done

• Review Kube and OpenShift documentation
• Review admin feedback session input in the research database 
• Review any other relevant deep dive research studies
• Ex. mental models 

• Competitive analysis 
• Share findings at IxD meeting(s) 
• Create High Level Design story