fix: lift nest and verdaccio parents, drop four obsoleted resolutions (#24675)

## Summary

Tier B of the resolutions audit: **two in-range parent lifts** whose
newer releases carry the fixes we were forcing by hand, letting **four
resolutions be dropped**. Prefer-parent-over-resolution, applied in
reverse: once the parent ships the fix, the force goes.

### 1. NestJS core quartet 11.1.24 -> 11.2.1 (lockstep)

`@nestjs/common`, `@nestjs/core`, `@nestjs/platform-express`,
`@nestjs/testing` move together. 11.2.0/11.2.1 are fixes plus two
additive features (query HTTP method, SSE signal) - no breaking changes,
peer ranges stay `^11.0.0`. `@nestjs/cli` stays locked at 11.0.16 (its
hold - the >11.0.23 dist/src regression - is unrelated and untouched).

platform-express 11.2.1 **pins multer 2.2.0 itself**, so:
- dropped: `@nestjs/platform-express/multer` - multer 2.2.0 now flows
through the parent.

### 2. verdaccio ^6.3.1 -> 6.10.0 (root devDep, in range)

Brings `@cypress/request` **4.0.1** (declares `qs ^6.15.2`, and **no
uuid dependency at all**) and `@verdaccio/config` **8.2.2** (pins the
fixed js-yaml **5.2.2** itself), so:
- dropped: `@cypress/request/qs`
- dropped: `@cypress/request/uuid`
- dropped: `@verdaccio/config/js-yaml` (the js-yaml doc entry goes from
seven pinners to the six `@mintlify/*` ones)

`//resolutions` updated in all four places, each recording why the entry
left.

## Verification

- multer resolves **2.2.0 via the parent**; qs resolves 6.15.2/6.15.3
only; uuid 11.1.1 + the intentional 13.x; js-yaml settles into three
fixed-line entries (4.3.1 mintlify-forced, 5.2.2 verdaccio's own, 3.15.1
legacy consumers).
- twenty-shared rebuilt, then `tsgo --noEmit` on twenty-server passes
(direct, cache-proof); `nx lint:diff-with-main twenty-server` passes.
- Auth service unit suites (real `@nestjs/testing` modules) pass on nest
11.2.1: 13/13.
- `yarn install --immutable` passes.