publish 1.9.2-canary.1 to registry

add included metadata to chunks to allow deduplicate chunk loads at r…

…untime (vercel#4488)

### Description

Chunk loading is now more than just a single chunk filepath. It might
consist of additional metadata which tells the chunk loading logic the
entry modules included in this chunk. This allows the runtime logic to
avoid loading chunks when all entry modules are already loaded.

This means loading the same chunk from multiple sources (with different
available modules) will only trigger a single load and so avoids
transferring more code than needed.

This is especially relevant in app dir where every client component is
considers as separate chunk loading.

next.js: vercel/next.js#48025

Revert "Chunking Context Refactor pt. 3: Address PR comments from pt.…

… 2" (vercel#4588)

Reverts vercel#4546

Revert "Chunking Context Refactor pt. 3: Address PR comments from pt.…

… 2" (vercel#4588)

Reverts vercel#4546

Revert "Chunking Context Refactor pt. 3: Address PR comments from pt.…

… 2" (vercel#4588)

Reverts vercel#4546

Revert "Chunking Context Refactor pt. 3: Address PR comments from pt.…

… 2" (vercel#4588)

Reverts vercel#4546

fix: better support for pnpm aliases (vercel#4555)

### Description

This is a follow up to vercel#4541 that fixes the underlying issue. We now
will attempt to return the extracted version instead of the full key
when we encounter one.

A quick explanation for how this happened is that when [pnpm
aliases](https://pnpm.io/aliases) are used the resolved version in the
lockfile will be the full lockfile key instead of a version since the
name won't match the specifier (e.g. `"foo: npm:bar@^1.0.0"` will have a
version of `/bar/1.0.0` instead of just `1.0.0`). This is all fine
unless an external dependency also depends on `[email protected]` then we get a
dependency of `Package{Key: "/bar/1.0.0", Version: "1.0.0"}` when going
through the external dependency where we would get `Package{Key:
"/bar/1.0.0", Version: "/bar/1.0.0"}` going through the workspace with
the alias.

### Testing Instructions

Updated the unit test added in the initial PR to reflect that we're no
longer getting a package with a version that's actually a lockfile key.
This change also changes the test for pnpm overrides, but this change is
more correct as we're now only returning the version. I also tested that
the changes don't trigger the repro that was provided in vercel#3638

fixup bind v6 PR: add missing listen call (vercel#4585)

### Description

need to call listen() on the socket

publish 1.9.2-canary.0 to registry

release(turborepo): 1.9.2-canary.0 (vercel#4576)

Co-authored-by: Turbobot <[email protected]>