Turbopack-loader implementation should be decoupled from webpack

[refirst11]

The under type was opted out.

import type { LoaderContext } from 'webpack'; // opt-out

New types ( Use only the minimum )

interface TurbopackLoaderContext {
  resourcePath: string;
  rootContext: string;
  context: string;
  clearDependencies: () => void;
  addDependency: (path: string) => void;
  async: () => (
    err: Error | null,
    content?: string | Buffer,
    sourceMap?: any,
  ) => void;
}

What makes you happy?

Webpack will be removed from turbopack-loader's devDependencies.

Reason

turbopack - next.config.js
The this injected by turbopack is mostly compatible with the loader-runner provided by webpack, but about 7 of them are not supported.

Turbopack uses the loader-runner library to execute webpack loaders, which provides most of the standard loader API. However, some features are not supported:

[refirst11]

The test passed -> test-e2e/ @playwright/test.
This proves that the type doesn't modify code at runtime.

[refirst11]

I will post here again once I have confirmed the exact behavior in the execution environment.

[refirst11]

In my environment, v2.0.0 worked without any problems.