OTA Upgrade documentation must include operator upgrade compatibility 

The current documentation for EUS-to-EUS is not clear what happens when:

• operators block the upgrade; because OCP/Kube versions wouldn't be met
• or when EUS to EUS upgrade could lead to outages (with operators simply not functioning because of the upgrade) if not done properly
• or How to safely exit from upgrade in case of issues.
• or Show information on the operator compatibility matrix
• also issue https://issues.redhat.com/browse/OSDOCS-3739
• When a customers wants to use the fast or stable channel of the release while waiting for the EUS release to be available.

customer needs updated upgrade documentation covering some of the recent concerns raised internally and externally.