[v2] Listener conflict with existing service

[ajssmith]

Describe the bug
When a listener is created, it will modify a pre-existing service with the same name as listener host.

How To Reproduce
Locally xxpose the backend deployment in the hello world example (e.g. east namespace). Then create a listener in the same namespace and observe the service is modified by the controller.

Expected behavior
Expectation is that the listener would not modify the pre-existing service. It should indicate the listener is not ready and provide the reason (e.g. detected existing service).

Environment details
Skupper V2.0.1 controller on kubernetes

[ajssmith]

A user work-around is to modify the listener host spec to prevent the conflict

[fgiorgetti]

When the service does not exist, the controller is currently adding:

annotations:
  internal.skupper.io/controlled: "true"

I agree. It should not touch a service that is not controlled.