chore: bump bundlewatch JS thresholds to match current bundle sizes

[mrholek]

The six JS bundle entries in `.bundlewatch.config.json` were slightly under the current gzipped sizes, so `bundlewatch` failed on every PR (e.g. `coreui.bundle.js` 108.5KB > 108.25KB). The growth is legitimate — accumulated component features — so the thresholds are raised to sit just above the current sizes with a small headroom:

Bundle	Current (gzip)	Old max	New max
`coreui.bundle.js`	108.5KB	108.25 kB	109.50 kB
`coreui.bundle.min.js`	61.83KB	61.75 kB	62.50 kB
`coreui.esm.js`	93KB	92.75 kB	94.00 kB
`coreui.esm.min.js`	60.99KB	60.85 kB	61.75 kB
`coreui.js`	94.61KB	94.25 kB	95.50 kB
`coreui.min.js`	54.85KB	54.85 kB	55.50 kB

CSS thresholds are unchanged (still passing). Verified locally with `npm run dist && npm run bundlewatch` → `bundlewatch PASS`.

[coveralls]

Coverage Report for CI Build 29294843918

Coverage remained the same at 94.635%

Details

• Coverage remained the same as the base build.
• Patch coverage: No coverable lines changed in this PR.
• No coverage regressions found.

Uncovered Changes

No uncovered changes found.

Coverage Regressions

No coverage regressions found.

---

Coverage Stats

Relevant Lines:	7462
Covered Lines:	7186
Line Coverage:	96.3%
Relevant Branches:	3088
Covered Branches:	2798
Branch Coverage:	90.61%
Branches in Coverage %:	Yes
Coverage Strength:	724.21 hits per line

---

💛 - Coveralls