[Infra + Logs UI] New platform client shim

[jasonrhodes]

As part of our new platform migration , we need to implement the core shim.

See here: https://github.com/elastic/kibana/blob/master/src/core/MIGRATION.md#introduce-new-plugin-definition-shim

AC:

• Infra and logs UI application start up (client-side) are both using a new platform core shim
• Implementation has been checked by the new platform team (@skaapgif probably?)

See here for more details on how this was done in APM: #34531

Notes:

Here is a list of dependencies we rely on that need to be added to the shim so that we can become fully NP-compatible. There are 72 instances of importing from ui/* across 49 files.

• ui/capabilities (21) ??

• ui/index_patterns (14) -> data.indexPatterns still in progress?

• ui/chrome (13)

  • import { Badge } from 'ui/chrome/api/badge'; + chrome.badge.set()
  • import { Breadcrumb } from 'ui/chrome/api/breadcrumbs'; + chrome.breadcrumb.set()
  • chrome.helpExtension.set()
  • chrome.addBasePath()
  • chrome.getUiSettingsClient().get('theme:darkMode');

• ui/kfetch (7) -> core.http

• ui/autocomplete_providers (3)

• ui/routes (3)

• ui/vis/lib/timezone (2)

• ui/utils/query_string (2)

• ui/modules (2)

• ui/i18n (1)

• ui/notify (1) toastNotifications -> core.notifications

• ui/registry/feature_catalogue (1)

• ui/new_platform (2)

[elasticmachine]

Pinging @elastic/infra-logs-ui