chore: drop four resolutions their parents no longer need (#24739)

## Summary

Follow-up to the resolutions audit. Four scoped pins are no longer
load-bearing: each parent now resolves to a fixed version on its own, so
the pin either duplicated the parent's edge or matched nothing.

| Dropped | Why it is dead |
|---|---|
| `googleapis-common/uuid: 11.1.1` | `googleapis-common@8.0.1` (forced
via `googleapis/googleapis-common`) has no `uuid` dependency at all. The
entry matched nothing. |
| `@react-email/ui/esbuild: 0.28.1` | `@react-email/ui@6.9.0` already
pins `esbuild@0.28.1` exact. |
| `react-email/esbuild: 0.28.1` | `react-email@6.9.0` allows `^0.28.0`;
the pin only existed while 0.28.1 was behind the `npmMinimalAgeGate`
(cleared 2026-06-14). |
| `storybook/esbuild: 0.28.1` | `storybook@10.4.6` widened its esbuild
range to include `^0.28.0` (the doc's "capped at ^0.27.0" was true at
10.4.4). |

`resolutions` goes 31 to 27. The `//resolutions` doc is updated to
match: the esbuild section now lists the three parents still pinning a
vulnerable esbuild (`@opennextjs/aws`, `zapier-platform-cli`,
`@lingui/cli` 5.x), and the uuid paragraph records that no uuid pin
remains.

## Verification

- `yarn.lock`: every one of the four parents keeps resolving to a
version at or above the fix (`esbuild >= 0.28.1`; no `uuid` edge on
`googleapis-common@8.0.1`). No package leaves the tree.
- `yarn install --immutable` passes.
- No workspace `package.json` changes, no new pins.