White-listing of telemetry params

[Iku-turso]

Motivation: make unexpected large params not eat resources.

With this, we can have white-list such as:

const whiteList = [
  ...
  // old types of white-list items, but now not resulting in any args as params of telemetry
  "navigate-to-extensions",
  "navigate-to-cluster-view",
  "navigate-to-entity-settings",

  // new type of white-list item, now with selectable args as params of telemetry
  {
    id: "navigate-to-route",
    getParams: (route: Route<unknown>) => ({ param: route.path }),
  },
];  

Note: also telemetry by tagging is dropped for not being used.

[aleksfront]

Can you describe what decorable is?

[Iku-turso]

It is a solution to make decorators, and their affiliates, not decorate themselves infinitely. We'll remove requirement for decorable eventually.

[aleksfront]

Motivation: make unexpected large params not eat resources.

Any advice where whitelisting params should be implemented very first?

[Iku-turso]

Any advice where whitelisting params should be implemented very first?

@aleksfront I suppose we could follow the white-list in /lens/packages/core/src/features/telemetry/renderer/telemetry-white-list-for-functions.injectable.ts, and start making some informed guesses :/

Eg. enable-extension and friends could benefit from name of extension. show-details could tell what details are being shown.