doc: remove extensionless CJS exception for type:module

[mcollina]

The CJS documentation has included an exception since v16 (added in #41383) stating that extensionless files in type: "module" packages are recognized as CommonJS when included via require(). This exception conflicts with the ESM resolution specification which states that extensionless files within a package scope with an explicit type field follow the format of the type field.

Since #61600, the behavior on main already matches the ESM spec: extensionless files respect the type field. This change aligns the CJS documentation accordingly by removing the contradicting exception.

For v25.x, #62083 restores the documented exception as a targeted fix to avoid breaking packages like yargs v17 that relied on the old behavior.

Refs: #61600
Refs: #62083
Refs: #61971

[nodejs-github-bot]

Review requested:

• @nodejs/loaders

[joyeecheung]

I think we can just removed this entire point, because the opening paragraph says:

Node.js will treat the following as CommonJS modules

Instead, just add a new paragraph noting that files with extensions outside that set/files without extensions would be treated based on the type field in the package.json

[GeoffreyBooth]

Suggested change

	CommonJS modules).
	By default, Node.js will treat the following as CommonJS modules:
	* Files with a `.cjs` extension.
	* Files with a `.js` extension or without an extension, when the nearest parent
	`package.json` file contains a top-level field [`"type"`][] with a value of
	`"commonjs"`.
	* Files with a `.js` extension or without an extension, when the nearest parent
	`package.json` file doesn't contain a top-level field [`"type"`][] or there is
	no `package.json` in any parent folder; unless the file contains syntax that
	errors unless it is evaluated as an ES module. Package authors should include
	the [`"type"`][] field, even in packages where all sources are CommonJS. Being
	explicit about the `type` of the package will make things easier for build
	tools and loaders to determine how the files in the package should be
	interpreted.
	* Files with an extension that is not `.mjs`, `.cjs`, `.json`, `.node`, or `.js`,
	when the nearest parent `package.json` file contains a top-level field
	[`"type"`][] with a value of `"module"`.