Port-Forwarding cleanups (#722)

As per https://github.com/minio/console/issues/2539 , the websocket
behavior integrated as part of Console 0.22.1
(https://github.com/minio/console/pull/2419) seems to break
port-forwarding behavior.

There's no easy fix for this. NodePorts are a workaround, but slightly
kludgy. Ingress is the better long-term solution, but requires more
work.

This is a stopgap:

- For Operator, point users towards NodePorts if port-forwarding fails
- For Tenant Console, simply drop port-forwarding entirely and point
only at Ingress/LB

Out of scope but in progress is Ingress guidance for Nginx and Traefik
so we can close the loop on this.

source/includes/openshift/deploy-minio-on-openshift.rst

@@ -153,20 +153,7 @@ You can find the MinIO Operator Interface from the :guilabel:`Operators` left-ha
 
 The MinIO Operator includes the Operator Console, a browser-based management interface for managed MinIO tenants.
 
-You can temporarily port-forward the Operator Console to your local host machine using the ``oc minio port-forward`` command:
-
-.. code-block:: shell
-   :class: copyable
-
-   oc minio port-forward
-
-The command returns a JWT token and a URL you can open in your browser.
-
-.. image:: /images/k8s/operator-dashboard.png
-   :align: center
-   :width: 70%
-   :class: no-scaled-link
-   :alt: Operator Dashboard
+.. include:: /includes/common/common-k8s-connect-operator-console.rst
 
 You can create a permanent routing rule by creating a :openshift-docs:`Route or Ingress <networking/understanding-networking.html#nw-ne-comparing-ingress-route_understanding-networking>` to allow access from external clients, such as your local computer browser.