[Breaking] Update IDs on plugins migrated to the new platform

[lukeelmers]

The ids contained in legacy package.json and index.js files of core_plugins are used for enabling/disabling plugins via kibana.yml config.

As part of the new platform migration efforts, we will be renaming/separating/combining some plugins into the structure outlined in the meta issue.

It would make sense to also update the IDs so that the names are consistent in yml config. This would technically be a breaking change, so this issue exists to track that all IDs have been changed in 8.0 and that the changes are properly documented for devs.

[elasticmachine]

Pinging @elastic/kibana-app-arch

[lukeelmers]

I did an audit of all app arch-owned plugins, and can confirm that no IDs need to be updated as these plugins are basically all new. (Other than checking to make sure naming is camelCase, but we already have a separate issue to track that)

When I created this issue originally, it was primarily with the legacy vis type plugins in mind, which were shuffled around a bit during migration.

@flash1293 I'll re-assign this to you & tag it for the app team. Feel free to close if you don't need it or are already tracking this elsewhere.

[flash1293]

Handled via your latest PR @lukeelmers - thanks!