NAS-142557 / 27.0.0-BETA.1 / Bump @truenas/ui-components to 0.7.1 and name unnamed spinners once

[AlexKarpov98]

Bumps @truenas/ui-components from ~0.5.1 to ~0.7.1 and does the work that bump requires.

What the bump broke, and the fixes

TN_DIALOG_LABELS / TnDialogLabels gone	renamed TN_DIALOG_CHROME_LABELS / TnDialogChromeLabels — the provider added on this branch no longer compiled
TnTableLabels gained 4 keys	sortAscending, sortDescending, expandRow, collapseRow — our bundle was partial, so those four would have shipped untranslated
performance.now missing in specs	setup-jest.ts replaces jsdom's performance with a mark/measure-only stub; 0.6+ calls performance.now() for its transition fallbacks, so every spec rendering a side panel or dialog threw
radio option test ids	an option now emits radio-button-<x>, not radio-<x> (NAS-142376) — only edit-nfs-ace selects options by test id; radio-group- ids are untouched and the e2e suite references neither
tooltip accessible name	TnFormFieldHarness.getTooltip() reads the help button's aria-label, and the library now strips markup out of it — an aria-label is announced verbatim, so <i> and <br> would be read out. The visible tooltip still renders them; the spec was comparing against the wrong one of the two

The four label providers added earlier on this branch had no spec. One now covers all of them and asserts each bundle against the library's own default bundle's key set, so the next release that adds a key fails here instead of shipping an English string to a translated app.

Naming the unnamed

0.7.x also warns, in dev mode, whenever a tn-spinner, tn-progress-bar, tn-dialog-shell or tn-side-panel renders with no accessible name — and jest-fail-on-console makes each warning a failing test. The library's fallbacks ("Loading", "Progress", "Dialog", "Side panel") were English literals with no way in, so the only per-site answer was an ariaLabel on each: about forty, most repeating their neighbours' string.

provideTnFallbackLabels fills the library's TN_FALLBACK_LABELS bundle from translated() once instead — the same shape as the select, autocomplete, dialog-chrome and table bundles this branch already provides. Providing it is also what stands the warning down, per the token's contract: an app-wide fallback is a decision, not a forgotten label. setup-jest registers the same token (via defineGlobalsInjections for Spectator specs, a global TestBed provider for the rest) so specs see the decision the app makes.

20 hand-written [ariaLabel] strings come out of the templates, four of which predate this branch. The 10 that stay read a signal or a field — a job's description, a Docker status, the app-loader's title — and say what no app-wide default can. The three dialogs that render [title]="" plus their own heading keep an explicit ariaLabel, since "Dialog" would be worse than the heading they already show.

The token itself shipped in 0.7.1 via iXsystems/truenas-ui-components#308.

Testing

Everything below is against published 0.7.1:

• tsc -p src/tsconfig.app.json and yarn buildng (AOT, templates included) clean
• eslint clean on every changed .ts and .html
• src/app/modules — 248 suites / 2437 tests
• src/app/pages by area — 757 suites / 5166 tests
• everything else under src/app — 110 suites / 782 tests
• Re-scanned all templates: 0 static [ariaLabel] strings left on a spinner or progress bar

https://claude.ai/code/session_01PP236cd5LPtgSVz1aiL8pm

[bugclerk]

Jira URL: https://ixsystems.atlassian.net/browse/NAS-142557

[codecov]

Codecov Report

❌ Patch coverage is 80.00000% with 7 lines in your changes missing coverage. Please review.
✅ Project coverage is 88.50%. Comparing base (1ba1031) to head (1468d1d).
⚠️ Report is 3 commits behind head on master.
✅ All tests successful. No failed tests found.

Files with missing lines	Patch %	Lines
.../app/core/providers/tn-fallback-labels.provider.ts	0.00%	7 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master   #13970      +/-   ##
==========================================
- Coverage   88.51%   88.50%   -0.01%     
==========================================
  Files        1889     1894       +5     
  Lines       71294    71327      +33     
  Branches     9204     9212       +8     
==========================================
+ Hits        63103    63129      +26     
- Misses       8191     8198       +7     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[github-actions]

Five findings, all LOW — nothing here blocks the merge. 🎉

Moving five bundles of library chrome copy onto DI tokens is the right shape: tn-dialog-shell's close/fullscreen buttons and tn-table's sort controls had no input to bind at all, so this is the only way they ever get translated, and the Record<keyof T, string> on each labelKeys makes a bundle that grows a key a compile error rather than a string that quietly ships in English. Deleting tn-select-labels.constant.ts and the ~200 template rows that re-bound it is a real subtraction — every tn-select in the app now gets the same wording without two attributes apiece. 👏 The performance.now() stub and its comment are a nice catch too.

The findings are all in the seams around that work, not the work itself:

• Only one of the five new tokens is mirrored into setup-jest.ts, so specs and production disagree on tn-select/tn-autocomplete/dialog/table copy — visible in the two specs this PR changed to assert a bare 'Select an option'.
• provideTnFallbackLabels is the one provider the new spec's bundle table skips, though TN_DEFAULT_FALLBACK_LABELS is exported and used a few lines away in setup-jest.ts.
• TN_FALLBACK_LABELS ends up registered twice in setup-jest.ts; the root beforeEach already covers Spectator specs, so the defineGlobalsInjections entry is dead.
• The five provider factories re-enumerate their keys after labelKeys already did, which the type system does not need.
• auth-section.component.spec.ts now hardcodes helptext fragments instead of deriving them from helptextUsers.

Details and suggested diffs are inline.

[bugclerk]

This PR has been merged and conversations have been locked.
If you would like to discuss more about this issue please use our forums or raise a Jira ticket.