GeezerVison

PR Checklist

• The PR title follows our guidelines: https://github.com/NativeScript/NativeScript/blob/master/tools/notes/CONTRIBUTING.md#commit-messages.
• There is an issue for the bug/feature this PR is for — fix(core): Android font-weight is ignored for custom fonts on API 26+ (no wght axis mapping) #11513.
• You have signed the CLA.
• All existing tests are passing — npx vitest run ui/styling/font.android.spec.ts (6/6); the new spec fails 4 of 6 cases against unpatched font.android.ts.
• Tests for the changes are included — packages/core/ui/styling/font.android.spec.ts.

What is the current behavior?

On Android API 26+, custom fonts loaded from files ignore CSS font-weight: loadFontFromFile passes only explicit font-variation-settings to Typeface.Builder.setFontVariationSettings, so a variable font with font-weight: 700 renders at its default weight. computeFontCacheKey also omits the weight, so two weights of the same family would collide in the typeface cache. And if a font doesn't support the wght axis, builder.build() throws with no retry — the file load fails outright.

What is the new behavior?

• A wght axis entry derived from fontWeight (getNumericFontWeight) is appended to the variation settings unless the caller set wght explicitly — explicit settings always win.
• fontWeight joins the typeface cache key, so weights of one family cache independently.
• If the augmented build throws, the load retries once with the caller's explicit settings (fonts that lack the wght axis still load). If the caller did request wght explicitly, the error propagates to the outer catch as before and the font falls back to the default typeface — no retry of a request the caller made.

Fixes #11513