elastic-package stack Kibana telemetry

### Summary
The Kibana started by `elastic-package stack up` sends telemetry out of the box. Building dashboard on top of these metrics, there is no way to differentiate legitimate data from test data as most of the metrics only contain a `cluster_uuid` to identify the cluster.

Should we disable telemetry ([telemetry.optIn](https://www.elastic.co/guide/en/kibana/master/telemetry-settings-kbn.html) setting) in elastic-package's Kibana to prevent mixing data ? Alternatively, could we store that data to a different index so production dashboard would not report irrelevant data (ie error rate of package installation in dev environment), maybe by routing it to a different telemetry cluster if that is possible ?

We can also ignore this and consider it a minor annoyance as testing data would not be noisy enough.
Thoughts ?

No implementation file or test is named. Start at the `elastic-package stack up` command and review how its Kibana instance is configured, then consult the linked `telemetry.optIn` setting documentation. Done requires a decided approach and verified separation or suppression of telemetry from production dashboard data.

Written by the indexing model from the issue text.