docs(pnp): remove pnpManifest (#176)

Author: stormslowly

README.md

@@ -173,7 +173,6 @@ The options are aligned with [enhanced-resolve](https://github.com/webpack/enhan
 | tsconfig.configFile |         | A relative path to the tsconfig file based on `cwd`, or an absolute path of tsconfig file.                                                                                                                                                                                                                                                                                                                 |
 | tsconfig.references | `[]`    | - 'auto': inherits from TypeScript config <br/> - `string []`: relative path (based on directory of the referencing tsconfig file) or absolute path of referenced project's tsconfig                                                                                                                                                                                                                       |
 | enablePnp           | false   | Enable Yarn Plug'n'Play support                                                                                                                                                                                                                                                                                                                                                                            |
-| pnpManifest         | None    | Absolute path to the Yarn Plug'n'Play manifest file; takes effect when PnP is enabled. <br/> - `None`: PnP manifest located in the nearest ancestor directory from every resolving's path; <br/> - `Some(PathBuf)`: Use a specific PnP manifest file. This is useful when enabling PnP with `enableGlobalCache: true`, but users must ensure there are no cross-project requires across Yarn PnP projects. |
 
 In the context of `@rspack/resolver`, the `tsconfig.references` option helps isolate the `paths` configurations of different TypeScript projects.
 This ensures that path aliases defined in one TypeScript project do not unintentionally affect the resolving behavior of another.