Simple plugin order

[liuxingbaoyu]

Q	A
Fixed Issues?	Fixes #1, Fixes #2
Patch: Bug Fix?
Major: Breaking Change?
Minor: New Feature?
Tests Added + Pass?	Yes
Documentation PR Link
Any Dependency Changes?
License	MIT

This PR isn't ready to be merged yet, but I thought it would be okay to have some discussions now.

This PR adds a top-level option sortPlugins, enabled by default in Babel 8, to control whether the order provided by the plugin is followed.

And added a plugin attribute orderData.

   orderData?: {
     id: string;
     version: number;
   } & {
     type: "list";
     data: () => string[];
   };

id and version are so that we can update the plugin order in patch versions, even if users are still using plugins that carry the old order data.

The sorting algorithm is very simple. From back to front, all plugins included in the order list are extracted and sorted, and inserted into the location of the first found plugin.
For example, A and B carry order data [A, B, C, D], but C does not.
[B,X,A] will be sorted as [X,A,B].
Because users almost always use preset-env, and presets run behind plugins, this will cause the plugins contained in preset-env to be collected at the end, trying to maintain compatibility.

This PR also shows an issue #16398 (comment) where our current plugin order breaks some block scoping.

Although this method is not very powerful, it can better maintain compatibility and meet the problems we currently encounter in built-in plug-ins. We can enhance it in Babel 9.

Maybe we should exclude them or use a separate list.

       "transform-modules-commonjs",
       "transform-modules-amd",
       "transform-modules-systemjs",
       "transform-modules-umd",

       "transform-typescript",
       "transform-flow",

[babel-bot]

Build successful! You can test your changes in the REPL here: https://babeljs.io/repl/build/56784