fix(client): apply selected units to bundle size filters - #2075

Motivation

In Bundle Size's Tree Graph, selecting MB for Asset Size or Module Size still applies a KB threshold. Both debounced handlers capture the initial unit, so a displayed threshold of 1 MB keeps a roughly 2 KB asset/module. Changing only the unit also leaves the previous byte threshold in effect.

Changes

Keep the entered numeric value in state and derive the byte limit from the current unit during rendering. Both filters now update when the unit changes, including when an input debounce is still pending; switching back to KB preserves and reapplies the displayed number.

Added six browser regressions using a real Rspack brief report with small and large assets/modules. They cover selecting the unit before typing, changing the unit after typing, a paused pending debounce, and switching back to KB. The large-module control remains visible above the 1 MB threshold.

Validation on Windows with Node 22.23.2:

• Built the unchanged baseline before editing and reproduced all six scenarios through the report UI.
• Client production build and its dependencies passed.
• All 74 existing client tests passed.
• All six new browser regressions passed using the existing Rstest/Playwright runner and local Chrome.
• Full rs check --type-check passed: lint/type checking for 735 files and formatting for 1018 files. The Windows checkout needed LF normalization to match Git's stored content; no unrelated content or lockfile changes are included.
• git diff --check passed.

AI assistance was used for diagnosis, implementation, and testing.