three.js R181 broken against "*" named in packages.md #51

There is a misalignment in package.json and other points in the Git repo (especially in the examples, but also in "core"):
"three": "*",
"@types/three": "^0.181.0"

Details:

"three": "*"
packages/core/package.json:95

"@types/three": "^0.181.0"
package.json:91
packages/core/package.json:92
examples/audio/package.json:25
examples/browser-first/package.json:26
examples/depth-occlusion/package.json:25
examples/environment-raycast/package.json:25
examples/grab/package.json:25
examples/layers/package.json:25
examples/locomotion/package.json:25
examples/physics/package.json:25
examples/poke/package.json:25
examples/scene-understanding/package.json:25

For better safety and stability, each version should be tested before allowing an untested choice or release. It should be:
"three": "0.185.0",
"@types/three": "0.185.0"

From R181 to R185, some APIs used have been redesigned, developed further, or changed more deeply. This may cause compatibility and stability issues if anyone gets the "latest" version from three.js through "three": "". The APIs used in R181 are:
Scene
Object3D
PerspectiveCamera
WebGLRenderer
Mesh
Material
Texture
Vector
Matrix*
Raycaster
GLTFLoader

During the bump, these are affected in the following ways (generic description):

• Minor internal API updates; no functional impact is expected:
  Scene
  PerspectiveCamera

• Internal API updates with changes to references and imports/exports from other routines or internals; tests are needed, but there should be no impact:
  Object3D
  Mesh
  Material
  Texture
  Vector*
  Matrix*
  Raycaster
  GLTFLoader

• Deeper API development, which may cause issues if the previous hybrid state */0.181.0 was used strictly or in borderline ways:
  WebGLRenderer
  renderer.xr
  shadow mapping
  transmission
  render targets
  depth / occlusion
  XR layers

Due to Murphy's Law, the biggest developments involve XR... :)

BTW, some other components included in PACKAGES.md are outdated (such as npm/pnpm; configuration files and RC environment variables were also changed, resulting in this test warning: "This will stop working in the next major version of npm. See npm help npmrc for supported config options.")

PS: The PR will be sent; no changelogs or version/revision fields will be touched. I have left a "test/" folder with all the scripts used to test and process the files as proof. I also did not touch "contributors" in package.md, since this will be a PR from a fork, not a direct contribution.
PPS: The MIT headers in the various files were inconsistent; I will provide aligned ones.