fix: lift @argos-ci/storybook to ~6.0.18, drop the sharp resolution, bump tiptap to 3.30.2 (#24728)

## Summary

Two commits:

1. **Lands the argos bump that #24698 described but did not ship, and
drops the resolution it added in its place** - `@argos-ci/storybook
6.0.6 -> ~6.0.18` in twenty-front + twenty-ui, `@argos-ci/core/sharp`
removed (32 -> 31 resolutions). `//resolutions` on main already
described this exact state ("bumping @argos-ci/storybook to ~6.0.18 ...
so no argos sharp resolution is needed"), so the doc becomes true with
zero edits. The tilde keeps us on the vitest-free 6.0.x line; confirmed
no `@argos-ci/vitest` in the tree.

2. **Bumps tiptap 3.4.2 -> 3.30.2 to fix the bubble-menu teardown crash
the argos bump exposed** (see below).

## The CI failure, and why tiptap

The first run failed `front-sb-test (2, modules)` with **175/175 tests
passing** but vitest exiting non-zero on **15 unhandled errors**:
`TypeError: Cannot read properties of null (reading 'domFromPos')` in
`@tiptap/extension-bubble-menu` `updatePosition` -> prosemirror
`coordsAtPos` on a destroyed editor view, all from
`WorkflowEditActionEmailBase.stories.tsx`. Main's last three runs of
that shard: zero.

Cause chain, verified:
- The only behavioral change in `@argos-ci/storybook` between 6.0.6 and
6.0.18 is 6.0.17/6.0.18's vitest plugin **re-fitting the story iframe
inside `beforeScreenshot`** (every other release is a version bump).
That layout mutation fires the BubbleMenu reposition while the story's
editor is already torn down.
- tiptap fixed exactly this upstream (ueberdosis/tiptap#7433 plus the
`updatePosition` guard against a destroyed view), but twenty-front
pinned its sixteen `@tiptap/*` packages at **3.4.2**, resolving
`extension-bubble-menu` **3.14.0** - from before the fix.

So argos surfaced a latent editor bug rather than causing one, and the
fix is the parent bump, not pinning argos below the change or muting
unhandled errors.

### What the tiptap commit does
- All sixteen `@tiptap/*` -> **3.30.2** in lockstep (3.30.3 is inside
the 3-day npm age gate).
- Tree deduped onto that one version: blocknote's `^3.13.0` copies and
twenty-emails' `^3.4.2` copy collapse onto 3.30.2 - the repo now carries
a **single tiptap version** (previously three: 3.4.2 / 3.14.0 / 3.20.0).
- `@tiptap/pm` 3.30.2 pulls `prosemirror-view` 1.42.2 while blocknote's
carets held 1.41.6; the two copies split `EditorView`'s type identity
(`UploadImagePlugin.ts`). `yarn dedupe prosemirror-*` collapses
view/history/transform onto single versions - **no source change**.

## Verification

- **The failing story, plus every `advanced-text-editor` story, run
locally with the argos 6.0.18 plugin active** (STORYBOOK_SCOPE=modules;
54 screenshots captured, so `beforeScreenshot`'s iframe-fit executed): 3
files / 27 tests pass, **zero unhandled errors, zero `domFromPos`**.
- `nx typecheck twenty-front` and `nx typecheck twenty-emails` pass
(cache bypassed, dependency dists rebuilt); `nx lint:diff-with-main
twenty-front` passes.
- `nx storybook:build twenty-ui` and `nx storybook:test twenty-ui` (the
CI screenshot step) pass: 81 files / 256 tests.
- Lockfile: `@argos-ci/core@6.4.0` declares `sharp ^0.35.2` itself;
sharp copies 0.33.5 / 0.35.2 / 0.35.3, no 0.34.x; single `@tiptap/*`
version 3.30.2; `extension-bubble-menu` dist carries the destroyed-view
guard.
- `yarn install --immutable` passes.

`server-integration-test (15)` on the first run is the Gmail
`contact-auto-creation-policy` suite, which fails identically on
unrelated branches (e.g. charles/migrate-read-consumers-to-orm-v2) - a
known flake, no server files in this PR.