cloudnative

Fixes #3581

This common-labels functionality made the CLI tool harder to use when
piping the output into other programs. The common labels would be printed
on STDERR, while the rest of the labels and log-lines were emitted on
STDOUT.
I don't think we need this functionality any more, now that we have the
--exclude-label option.

Checklist

• Documentation added removed and

On contexts with many APIs and APIs calling other APIs in chains, having too many spans in the zipkin/jaeger dashboards may lead to a too complex usage of such dashboards and of not necessary big data volumes.

For Tyk's admin team, the steps representing the time spent in each Tyk middleware are much valuable.

But the upstream APIs teams just want to know the global time spent in Tyk interna

What's the problem
The default kubeconfig is ~/.kube/config. This default setting should works for all command tools related with K8s, like helm/kubectl. But vela CLI don't support that.

Solution I want
When KUBECONFIG not set, vela cli should read default config file.

What would you like to be added:
now, we have one integrate test example, add more

Why is this needed:

Is mushop validated against latest version of istio 1.10.x? The steps will defer from enabling kali/jageur etc which the docs is not updated.