Don't hoist past nested worktrees

[KeaganErasmus]

We have a Yarn v1 project that we want to upgrade to Yarn 3. This project is a monorepo with several server-side workspaces and two front-end workspaces. The front-end depends on Angular 12, which cannot handle having its components (@angular/*) installed into different directories. Using Yarn v1, we seem to have the right hoisting setup so that everything is hoisted correctly and the Angular code compiles fine.

The structure looks similar to this:

└── packages
    ├── frontend-a
    ├── frontend-b
    ├── frontend-c
    ├── server-a
    ├── server-b
    └── server-c```

After we upgraded our project to Yarn v3, when we run `yarn install` most of the Angular components are still hoisted to the root however the `@angular/compiler-cli` is not hoisted and stays in the front-end workspace. This prevents the Angular app from building.

An idea we came up with was to move the front-end workspaces into a separate nested worktree, e.g. `packages->frontend->app`, and have Yarn hoist the dependencies to the frontend worktree.

The proposed structure would look like:
```.
└── packages
    ├── frontend-worktree
    │   ├── frontend-a
    │   ├── frontend-b
    │   └── frontend-c
    ├── server-a
    ├── server-b
    └── server-c```

Should yarn support a new `nmHoistingLimits` option of `worktree`, which would find the nearest worktree belonging to a package and not hoist past there?

Alternatively, if the community has a better way of achieving this solution today we would be very interested to hear it!