[Meta] Prepare BeatsCM for new platform

[mattapperson]

This ticket outlines the necessary work to migrate to the new platform.

NOTE: This is a work in progress list and will be updated over time.

Timeline (these are all approximates and not set in stone)

Note: "Shims" are not needed as an intermediary step for BeatsCM. The adapter based architecture serves the same goals already.

7.7 (Estimated 2 - 4 days effort depending on unresolved issues)

Steps necessary for migration

Waiting on the following features from new platform in order to begin work

• savedObjects client, mappings, and migrations Migrate saved object service #33587
• server.plugins.security.getUser (available in NP Security plugin, legacy plugin utilizes it under the hood)
• License plugin License plugin #18356
• chrome.getKibanaVersion Expose packageInfo to the new platform plugins #45262 (We can work around this, but would really rather not)
• Client side security plugin [New platform] Security plugin integration #33775
• Sort out [BeatsCM - NP] A way to check user roles in client and server #47362

Create a replacement for client kibana_framework_adapter.ts

• Move from XPackInfoProvider to License plugin
• Migrate renderUIAtPath from the Angular to Application service
• remove manageAngularLifecycle

Create a replacement for server kibana_framework_adapter.ts

• Move all server.plugins.* calls to new platform
• Migrate from server.plugins.security.getUser API to getUser from new platform
• Move registerRoute to use new platform server API
• Move exposeStaticDir to use new platform server API

[elasticmachine]

Pinging @elastic/integrations (Team:Beats)