How to support import builtin plugins

[hardfist]

currently we start deprecating builtins options in favor of builtin plugins, but it brings another problem, how we import builtin plugin

• import from @rspack/cli
  this is simple, we just need to expose builtin plugin from @rspack/core to @rspack/cli, but it makes @rspack/cli coupled with api.

import { rspack, defineConfig } from '@rspack/cli';

export default defineConfig({
  plugins: [new rspack.DefinePlugin({
   "process.env.NODE_ENV": JSON.stringify(process.env.NODE_ENV)
  })]
})

• import from @rspack/core
  this means you need to install @rspack/core twice, once for @rspack/core and another for @rspack/cli(since @rspack/cli depends on @rspack/core)

import { rspack, defineConfig } from '@rspack/core';

export default defineConfig({
  plugins: [new rspack.DefinePlugin({
   "process.env.NODE_ENV": JSON.stringify(process.env.NODE_ENV)
  })]
})

• import from @rspack/core and make @rspack/core peerDep of @rspack/cli
  this means you need to install @rspack/core and @rspack/cli for simple apps, but this is the most compatible way with webpack, since webpack needs to both install webpack-cli and webpack and when we're compatible with webpack-cli, we may not need to maintain rspack-cli.

[hardfist]

we decide to choose the 3rd way to solve this problem and will ship this in 0.4.0