Add support for reporting destination Kubernetes service

[orishoshan]

Description

This PR adds the capability for the network mapper to keep the information it gets regarding pod-to-service connections. Previously, when the network mapper saw a Kubernetes service, it would resolve through the service to the destination pods. This additional information is useful for display and makes it easier to understand which Kubernetes service the intents are referring to. In addition, it is designed to be used with a new experimental feature in the intents-operator, which enables you to specify a Kubernetes service in intents. This is not only more readable, but it also makes it possible to add a port restriction to the network policy. The target port specified by the Kubernetes service will be used in the resulting network policy.

Coupled with an accompanying change in the Otterize network-mapper CLI, it will be possible to export intents that target Kubernetes services.

References

Intents operator pull request: otterize/intents-operator#256

Testing

• This change adds test coverage for new/changed/fixed functionality

Checklist

• I have added documentation for new/changed functionality in this PR and in github.com/otterize/docs
  This change is experimental and API-only at this time, as we are still figuring out the schema for the ClientIntents.