chore(perf): re-record the editor bundle baseline

[Pfannkuchensack]

Summary

main fails the frontend build budget since #9886 (and #9868) landed: the editor route's initial assets are over the 1 % allowance above the baseline captured on 2026-10-11, so every pull request against main fails frontend-webv2-tests in the architecture performance check. This re-records the architecture baseline at the current size; nothing else changes.

Route	Metric	Baseline	Now
editor	initial raw	3 226 866	3 266 960 (+40 094, +1.2 %)
editor	Brotli	1 177 491	1 189 581 (+12 090)
editor	gzip	1 170 684	1 182 627 (+11 943)
second route	initial raw	2 048 139	2 051 780 (+3 641)

No new initial chunks, sources or owners; request counts are untouched (the browser baseline is not part of this change).

Related Issues / Discussions

Unblocks open PRs whose CI fails only on this budget, e.g. #9914, #9916, #9923, #9924.

QA Instructions

On main at f1b24db, from invokeai/frontend/webv2:

• pnpm test:performance:build before: fails with editor initial raw assets reached 3266960 bytes/requests (limit 3259135, captured 3226866) (plus the Brotli/gzip lines).
• pnpm test:performance:build:update-baseline, then oxfmt on the baseline file.
• pnpm test:performance:build after: passes. pnpm lint: passes.

Review

The growth is from features already merged and reviewed (mainly the media-type filter for gallery and image map in #9886). If the team prefers to win the bytes back instead (the check suggests deepening widget-registry loading), this PR can be closed in favour of that.

Checklist

• The PR has a short but descriptive title, suitable for a changelog
• Meaningful regression coverage added / updated where needed; obsolete tests/code removed
• Persisted-state and API changes include required migrations / compatibility validation
• Relevant performance/efficiency opportunities considered; material claims have evidence
• Material review findings resolved and relevant checks rerun
• Documentation added / updated (if applicable)
• Updated What's New copy (if doing a release after this PR)

---

^{Need help on this PR? Tag @codesmith-bot with what you need.}