[Maps] Add ordering to layer wizard registration API

[thomasneirynck]

The layer-wizard registration API is exposed to other plugins.

There is no guarantee of the order in which the wizards are displayed in the UX, because there is no guarantee in the order in which plugins will call this API. e.g. they might even call it before the Maps-app registers its own layer-wizards.

The practical result is that layer-wizards from other plugins would end up "on top", where the Maps-app would still want to surface its own wizards first (e.g. upload GeoJson-wizard should come on top).

This was revealed in #122862.

By default, the ordering is set to 0.

Clients using the registerLayerWizard API would have to set the order param. This will allow us to enforce an ordering of layer-wizards.

e.g. in #122862, we'd set the order: 100 so the wizard does not surface on top.

[elasticmachine]

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

[thomasneirynck]

piggy-backing of this PR, but not really related to the ordering-issue. But the export of these types is required for #122862 as well

[alvarezmelissa87]

LGTM ⚡ 🙏

[nreese]

Should order be required? Should we set order for existing maps wizards? Now order is registration order. Maybe this would be better coded with values. Maybe maps plugins should start at 100 and manually set numbers above that. Then plugins could use 0-99 to register before maps wizards ad 200+ to register after maps plugins.

[thomasneirynck]

after discussion:

See proposal:

• 0-99: reserved for maps plugin
  • 10: maps-specific wizards
  • 20: solution layers
• 100+: non-Maps client plugins

Happy to make changes/tweaks

[nreese]

LGTM
code review

[kibana-ci]

💚 Build Succeeded

• Buildkite Build
• Commit: e39ff1f
• Storybooks Preview

Metrics [docs]

Public APIs missing comments

Total count of every public API that lacks a comment. Target amount is 0. Run node scripts/build_api_docs --plugin [yourplugin] --stats comments for more detailed information.

id	before	after	diff
maps	207	213	+6

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id	before	after	diff
maps	2.5MB	2.5MB	+153.0B

Public APIs missing exports

Total count of every type that is part of your API that should be exported but is not. This will cause broken links in the API documentation system. Target amount is 0. Run node scripts/build_api_docs --plugin [yourplugin] --stats exports for more detailed information.

id	before	after	diff
maps	30	28	-2

Page load bundle

Size of the bundles that are downloaded on every page load. Target size is below 100kb

id	before	after	diff
maps	36.7KB	37.1KB	+373.0B

Unknown metric groups

API count

id	before	after	diff
maps	208	214	+6

History

• 💔 Build #17401 failed c81182e
• 💔 Build #17383 failed 7fc4fc4

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