Support non-transparent proxy outbounds

[johncowen]

Description

Currently I don't believe we support non-transparent proxy outbounds anywhere in the GUI. i.e. we don't display them anywhere.

Off the top of my head the only place we show outbounds is in the Dataplane Overview/Visualization, and these are outbounds on services using transparent proxy which are inferred/derived from the Envoy /stats API rather than using outbounds explicitly provided/configured in YAML config.

We should also support non-transparent proxy based outbounds, i.e. those provided via a Dataplane config such as:

type: Dataplane
mesh: default
name: dp-wordpress-1
networking:
  address: 10.0.0.1
  inbound:
  - port: 8000
    servicePort: 80
    tags:
      kuma.io/service: wordpress
      kuma.io/protocol: http
  outbound:
  - port: 6379
    tags:
      kuma.io/service: redis

Some finer points/queries:

1. Currently this summary panel can already get pretty full of information (see below for screengrab of current state). Therefore, if we are to display Outbounds in the Dataplane Summary panel, then we should probably consider using our "Tabs within summary panels" UX i.e. [Overview/YAML] [Inbounds] [Outbounds]

2. Should we also make sure that the Dataplane Overview Visualization supports both Envoy /stats inferred outbounds and explicit config/yaml defined outbounds?

[lukidzi]

Triage: if we are using stats API of Envoy we should be able to see them.

[jakubdyszkiewicz]

Triage: Dataplane wiz will just work. We want to add outbound to summary card after inbounds.