Context

https://github.com/redhat-developer/red-hat-developers-documentation-rhdh/pull/700#issuecomment-2493906401 

Description

RHIDP-2707 is clarifying that the Operator installation requires OLM. As such, it removes the non-OLM steps for deploying the operator on EKS.

As a follow-up ( https://issues.redhat.com/browse/RHIDP-2707?focusedId=26065025&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-26065025 ), we should also update the instructions for AKS: https://docs.redhat.com/en/documentation/red_hat_developer_hub/1.3/html/installing_red_hat_developer_hub_on_microsoft_azure_kubernetes_service/proc-rhdh-deploy-aks-operator_title-install-rhdh-aks#proc-rhdh-deploy-aks-operator_title-install-rhdh-aks

Right now, the first step in this procedure is `Obtain the Red Hat Developer Hub Operator manifest file, named rhdh-operator-<VERSION>.yaml [...]` (with no information on how to obtain that manifest), then `Apply the modified Operator manifest to your Kubernetes cluster`. There is no mention of OLM there.

NOTE: The instructions to install the Operator with OLM should be quite similar on AKS and EKS, so it might be worth refactoring and reusing content in both docs (I'm not sure if the last step on changing the Service Type to `NodePort` is needed on AKS).