Management advanced settings telemetry

[lizozom]

Summary

Report UI Settings, which differ from their default values in telemetry, in order to be able to track setting usage.

For Kibanas with multiple spaces defined, the settings reported in telemetry are of the default space only.

Also tested fields appear in actual telemetry report:

In order to use this data in our telemetry dashboards, we need to map interesting advanced settings to fields.

@AlonaNadler FYI this will be available in v7.6

Checklist

Use strikethroughs to remove checklist items you don't feel are applicable to this PR.

• This was checked for cross-browser compatibility, including a check against IE11
• Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support
• Documentation was added for features that require explanation or tutorials
• Unit or functional tests were updated or added to match the most common scenarios
• This was checked for keyboard-only and screenreader accessibility

For maintainers

• This was checked for breaking API changes and was labeled appropriately
• This includes a feature addition or change that requires a release note and was labeled appropriately

[elasticmachine]

Pinging @elastic/kibana-app-arch (Team:AppArch)

[kibanamachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request
• Commit: fdaaba9

History

• 💔 Build #19052 failed 3926d78beb76ae1693a8926b7ba919db64257e04

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

[Bamieh]

LGTM! I've also pulled the code and checked the usage data on the default space:

With custom settings:

No user specific changes:

I did not test this across spaces.