[Maps] Migrate Maps server to NP

[kindsun]

Pulling this out as a separate PR from #65079 since it has a pretty large footprint on its own. Migrates the remaining pieces on the Maps server side to NP. Includes:

• Telemetry
• Server-side routing
• Basic server-side query/params validation
• Sample data registration
• Tutorial registration
• Return config from client and server setup
• Remove getInjectedVarFunc references and connect map config
• Reduce legacy plugin init to a minimal presence required for plugin registration
• Many other connecting pieces

There are a few aspects of Maps in NP worth future passes that I noticed during this migration. I'll generate issues for several I've listed below and any others I think of. Offhand, this might include:

• Now that we're leveraging the new server-side router, take further advantage of router validation
• Organize server/plugin.ts. Maybe move sample data and tutorial registration to a separate file
• Audit config handling (related)

[elasticmachine]

Pinging @elastic/kibana-gis (Team:Geo)

[nreese]

I am getting the error "log [16:32:45.317] [fatal][root] { ValidationError: child "xpack" fails because [child "maps" fails because ["showMapsInspectorAdapter" is not allowed]]" with xpack.maps.showMapsInspectorAdapter: true. How do you set xpack.maps.showMapsInspectorAdapter now?

[kindsun]

I am getting the error "log [16:32:45.317] [fatal][root] { ValidationError: child "xpack" fails because [child "maps" fails because ["showMapsInspectorAdapter" is not allowed]]" with xpack.maps.showMapsInspectorAdapter: true. How do you set xpack.maps.showMapsInspectorAdapter now?

Something's broken here, I see it's failing tests as well. Will look into it! Fixed. We weren't able to complete remove legacy config validation so long as we have some code in legacy. We need some validation as a placeholder while there's a legacy presence for tests.

[kindsun]

@thomasneirynck @nreese This is ready for another pass when you have a chance. A few things to note since this was last reviewed:

• @nreese requested updates to config naming have been made
• Even though we're handling configuration serving and validation in NP, so long as we have any presence in legacy, some sort of basic config validation must be present for tests. I've updated x-pack/legacy/plugins/maps/index.js with the recommended placeholder configuration for tests
• Pass new maps config from legacy for service init
• Any TS-specific warnings in legacy client code have been ignored since these files will all be going away anyway in [Maps] Migrate maps client router to react #65079
• Updated how config is obtained for compat with karma tests which load the app in a different way where you can't rely on np plugins having been created for legacy import.
• Added some basic route validation for query and params on server routing

[nreese]

Just one comment remaining about removing some ts-ignore

lgtm
code review, tested in chrome

[kibanamachine]

💚 Build Succeeded

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

History

• 💚 Build #49206 succeeded db5a3a2
• 💚 Build #49156 succeeded 6a54a1f
• 💚 Build #49008 succeeded 223471e
• 💔 Build #48975 failed 0321801
• 💔 Build #48961 failed c8f61f4

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