[preset-env] Add targets for dynamic import

[nicolo-ribaudo]

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

In engines which support import() natively, it doesn't need to be transpiled. For example, someone might write this code:

import color from "./static-module";

main();
async function main() {
  if (!window.$) await import("jquery-cdn");

  $("body").css("background", color);
}

and it could safely become

define(["./static-module", function(foo) {
  main();
  async function main() {
    if (!window.$) await import("jquery-cdn");

    $("body").css("background", color);
  }
});

NOTE: I'm not 100% sure that this PR is correct. If someone doesn't want import() to be transpiled, you might argue that they shouldn't transpile static imports neither and thus use modules: false

[babel-bot]

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

[JLHwung]

Note that we have implemented similar checks for export-ns-from: #11849 I will see if I can revive this PR and targets for next minor release.

[nicolo-ribaudo]

I don't think anymore that this is something that we should do. We should not implicitly mix two module systems (esm and something else). It's usually a mistake, and if someone really wants to do it they can already explicitly disable proposal-dynamic-import.