`corepack enable` exits successfully (exit code 0), but isn't actually enabled

Issue

@Tobbe ➜ /workspaces/redwood (main) $ yarn -v
1.22.22
@Tobbe ➜ /workspaces/redwood (main) $ yarn
error This project's package.json defines "packageManager": "yarn@4.3.0". However the current global version of Yarn is 1.22.22.

Presence of the "packageManager" field indicates that the project is meant to be used with Corepack, a tool included by default with all official Node.js distributions starting from 16.9 and 14.19.
Corepack must currently be enabled by running corepack enable in your terminal. For more information, check out https://yarnpkg.com/corepack.
@Tobbe ➜ /workspaces/redwood (main) $ corepack enable
@Tobbe ➜ /workspaces/redwood (main) $ yarn
error This project's package.json defines "packageManager": "yarn@4.3.0". However the current global version of Yarn is 1.22.22.

Presence of the "packageManager" field indicates that the project is meant to be used with Corepack, a tool included by default with all official Node.js distributions starting from 16.9 and 14.19.
Corepack must currently be enabled by running corepack enable in your terminal. For more information, check out https://yarnpkg.com/corepack.
@Tobbe ➜ /workspaces/redwood (main) $ corepack prepare
Preparing yarn@4.3.0...
@Tobbe ➜ /workspaces/redwood (main) $ yarn -v
1.22.22
@Tobbe ➜ /workspaces/redwood (main) $ corepack install -g yarn@latest
Installing yarn@4.3.1...
@Tobbe ➜ /workspaces/redwood (main) $ yarn -v
1.22.22
@Tobbe ➜ /workspaces/redwood (main) $ yarn
error This project's package.json defines "packageManager": "yarn@4.3.0". However the current global version of Yarn is 1.22.22.

Presence of the "packageManager" field indicates that the project is meant to be used with Corepack, a tool included by default with all official Node.js distributions starting from 16.9 and 14.19.
Corepack must currently be enabled by running corepack enable in your terminal. For more information, check out https://yarnpkg.com/corepack.

Every command (except running just yarn) above exited with code 0. But none of them seems to actually do anything.

Expected behavior

Ideally corepack enable would work, and yarn would switch to version 4.3, but at the very least some kind of error message would be useful when corepack can't actually be enabled.

Additional Info

corepack yarn -v correctly prints out 4.3.0

Reproduction

1. Go to https://github.com/redwoodjs/redwood
2. Press . on your keyboard to open the redwood repo in an in-browser editor
3. Set up a new codespace
4. In the terminal, run corepack enable and yarn install

Workaround

Always use corepack yarn instead of just yarn

Reproduce the codespace scenario from the issue, starting with corepack enable, yarn -v, and corepack yarn -v. Trace the corepack enable entry point and compare its behavior with the working corepack yarn path; done means the command either activates the expected Yarn version or reports why it cannot.