Universal with MeshService should not require kuma.io/service

[lukidzi]

Description

While testing MeshService on Universal, I noticed that even though MeshService is supposed to work without requiring kuma.io/service, there is currently no way to support this. The dataplane validator enforces the presence of kuma.io/service and later generates a MeshService using its value as the name. Additionally, if we manually create a MeshService to select a specific dataplane with the same name as kuma.io/service, a conflict occurs because the generator attempts to create a MeshService with kuma.io/service

How should we behave?
Maybe instead of using kuma.io/service, we should generate a MeshService using the name of the dataplane and all its inbound ports, rather than relying on kuma.io/service?

[lukidzi]

Triage: we are using kuma.io/sevice for certificates and over multiple places. We should probably work on identity of the dataplane