fix: map every logical border property onto a prop React Native reads

[YevheniiKotyrlo]

Problem

On main:

1. border-block-color lands on two key sets. border-block-color: red writes borderBlockColor, and red blue writes borderTopColor / borderBottomColor. A later border-top-color then sits beside the axis key instead of replacing it, and Android and iOS rank borderBlockColor against borderTopColor oppositely, so the two platforms paint different colours. border-block writes borderBlockColor too.
2. A var() keeps the axis colours and the six logical shorthands off the parsed path. border-inline-color: var(--c) writes borderInlineColor, which React Native has no prop for. border-block-color: var(--c) with --c: red blue writes borderBlockColor: ["red", "blue"]. border-inline: var(--b) reaches React Native as borderInline: [2, "solid", "red"], and border-block-start: var(--b) as borderBlockStart the same way.
3. A var() edge style warns. border-inline-style: var(--tw-border-style), which every Tailwind v4 border-{x,s,e}-* utility emits, warns where the parsed path drops solid quietly, and border-block-style: dotted dashed names the inline edges in its warning.

Solution

• Each axis colour lands on its edge pair at every arity: the inline axis on borderStartColor / borderEndColor, the block axis on borderTopColor / borderBottomColor. Each edge parses its own colour, so a light-dark() component opens its dark rule over the edge it feeds.
• border-block-color, border-inline-color and the six logical shorthands resolve a var() at runtime onto the same keys, reading as many values as the variable substitutes, as border-inline-width already does.
• A var() edge style drops as quietly as solid, and a two-value edge style names its own edges.
• A runtime-parsed value that compiles to nothing declares nothing; border-inline-color: inherit left an empty style.

Tests

• src/__tests__/compiler/logical-borders.test.ts pins every logical property on the parsed path and the runtime call each var() compiles to.
• src/__tests__/native/logical-borders.test.tsx renders each: one key set per property under every cascade order and condition, each var() shorthand, a pair through one var(), a substitution the grammar does not take, and light-dark() on the parsed path.
• On main, 80 of the 276 cases in these files and borders.test.tsx fail. Each of 10 mutations fails its own cases.
• Every expectation is what Chromium 153, Firefox 155 and WebKit 26.6 compute for the same CSS.

Verification

On Ubuntu with the workflow's steps - build, lint, typecheck, yarn test, node --test node/__tests__/*.mjs, both library builds, the web export, the unstaged-changes checks and commitlint - everything passes.

Device evidence, before and after: #393 (comment)

Known limits

• A light-dark() holding a var() inside border-block-color or border-inline-color reaches the runtime handler, where light-dark() has no runtime resolver yet; fix: resolve light-dark() at runtime from the used colour scheme #420 adds one. main writes both of its halves to keys React Native lacks.

Merge order

This builds on #474, which resolves every declaration in cascade order, so a runtime shorthand leaves a later longhand its keys. It lands first, and this carries its commits until it does.

It also shares lines with #389 (native/styles/calculate-props.ts), #391 (compiler/declarations.ts, native/styles/calculate-props.ts), #411 (native/styles/calculate-props.ts), #420 (compiler/declarations.ts, compiler/stylesheet.ts); whichever lands second rebases.

It also shares lines with #488 (native/styles/calculate-props.ts); whichever lands second rebases.

It also shares lines with #495 (compiler/declarations.ts); whichever lands second rebases.

Base

Re-written on main (a5002c5), which carries #379's inline longhand renames through #451, so this targets main instead of fix-logical-border-props. #451 also renames the block widths, drops the per-edge styles and resolves border-block-width / border-inline-width at runtime; this builds on that in place of its own compile-time expansion.

[YevheniiKotyrlo]

Device evidence — before / after

UNFIXED — The three-part shorthand row paints no border — expanded from a var(), it sets neither edge. The width-only row above it paints on both builds.

FIXED — Both subject rows have a border on BOTH inline edges, matching the control.

before — 3.1.0-rc.0	after — with this PR

Android 16 emulator (API 36, GLES on the host GPU), 1140×2400 @ 480dpi, both frames from one run. before is the published 3.1.0-rc.0 plus what my test app needs from my other patches to run: the native and native-internal subpath exports, PR 459, cascade-layer ranking, and a shim that compiles a class-qualified :root inert. after adds the rest of my open PRs, this one included. One of them shows on every screen: PR 417 narrows a var()-valued font-family to one family, so the after sets its text in the theme's face where the before falls back to the platform's.