fix(preset-mini,preset-wind4): key the breakpoint cache by kind - #5303

Description

resolveBreakpoints takes a key selecting breakpoints or verticalBreakpoints, but memoizes into a WeakMap keyed only on the theme object:

if (resolvedBreakpoints.has(theme))
  return resolvedBreakpoints.get(theme)

The breakpoints variant calls it with the default horizontal key for every token during variant matching, and variant matching always runs before rule matching. So by the time h-screen-<point> asks for the vertical set, the entry is already populated with the horizontal one and the vertical values are silently ignored.

Isolated, on one theme:

call 1 (horizontal, as the variant does first): [ sm: 640px, md: 768px ]
call 2 (vertical,   as h-screen-* asks):        [ sm: 640px, md: 768px ]   <- should be 400px / 500px

End to end, with verticalBreakpoints: { sm: '400px', md: '500px' }:

- .h-screen-md{height:500px;}     expected
+ .h-screen-md{height:768px;}     actual
- .h-screen-sm{height:400px;}     expected
+ .h-screen-sm{height:640px;}     actual

This is deterministic rather than order-dependent, and it stays hidden with the shipped defaults because verticalBreakpoints starts as a copy of breakpoints. It only surfaces once a user customizes them differently, which the h-screen-$verticalBreakpoints autocomplete and the typed theme key both invite.

Change

The cache becomes a Map keyed by the breakpoint kind, so the two sets no longer share an entry. Applied identically to preset-mini and preset-wind4, which carry the same function.

Tests

One test per preset, asserting h-screen-sm/md follow the vertical set while w-screen-sm still follows the horizontal one, so an over-correction that swapped both would also fail.

Reverting only the two source files and rebuilding the presets fails both with .h-screen-md{height:768px;} against the expected 500px; restoring passes. Full preset-mini and preset-wind4 suites pass 46/46, and eslint is clean on the changed files.