Update test plans to use secured connectivity with the operator

[gabriel-farache]

Update test plans to use secured connectivity with the operator + rename edgedeployment in edgeworkload

[masayag]

installing MetalLB + defining address pool will provide an IP address from the local subnet of the node using service type LoadBalancer.
Then that IP can be accessed by port-forwarding.
see

• https://metallb.universe.tf/installation/
• https://metallb.universe.tf/configuration/#layer-2-configuration
  and OCP admin guide for it:
• https://docs.openshift.com/container-platform/4.9/networking/metallb/about-metallb.html

[gabriel-farache]

I'll take a look to those links and update the README, in the meantime, I'll remove this yaml file

[gabriel-farache]

Now that I understand better MetalLB, I fail to see why this is better than creating a NodePort. I mean, in this context of testing, I do not think that it is better to install MetalLB, create an AddressPool and a LoadBalancer servcice and then run port-forward, it's a lot of steps to have the same output IMO.
In fact, a simple port-forward added in the run script will be better as operator should be accessible on 127.0.0.1 or domain name project-flotta.io ==> by using port-forwarding, we can use 127.0.0.1 as address so we won't have issue with the certificates CN/alternateNames checks