Make PARTNER_API_ROOT dynamic in OEG partner requests

OEG currently injects PARTNER_API_ROOT as a configuration parameter (env var). In dual-OOP or multi-OP setups, the partner URL is cluster-specific (often a remote NodePort/LB). Hardcoding a single default is not correct because you need to pass the URL of the Federation Manager by configuration and in my opinion should passed as a parameter in the URL.

For now, there is a hotfix to make it work in the all-in-one deployment: integration@0f2945f6

Another quick workaround is to update the env var in the pod directly with:

➜  OperatorPlatform kubectl set env -n oop deploy/oegcontroller PARTNER_API_ROOT=http://federation-manager.federation-manager-remote.svc.cluster.local:8989
deployment.apps/oegcontroller env updated
➜  OperatorPlatform kubectl rollout restart -n oop deploy/oegcontroller
deployment.apps/oegcontroller restarted