templates: a required marker is coloured by a token Harmonia defines (#7155)

[delchev]

The * beside a required field's label on the four self-service views (my-form-view, my-document-view, partner-form-view, partner-document-view) carried class="text-destructive" — a Tailwind-shaped name with zero occurrences in the pinned Harmonia dist, where the token is negative.

An undefined utility class is not an error anywhere: the asterisk still rendered, in the inherited text colour. So on exactly those four surfaces it read as a literal character beside the label instead of the required signal the power manage/form-view and document/document-view show in red — and only there, which is what let the drift live.

The change

Both markers on each of the four move to text-negative:

• the one on the checkbox branch (added by ui: a boolean field renders as a checkbox, not an empty text box (#7103) #7114 / issue ui: a boolean field renders as a text input on the personal create/edit form #7103), and
• the pre-existing one on the generic label two lines above, which was equally wrong.

All sixteen required markers across the seven generated Harmonia surfaces now carry the same class.

The guard

HarmoniaRequiredMarkerIT (HTTP-free, boots no context — the HarmoniaDateFormatIT shape) asserts the two things the drift needed:

• every marker on every surface carries the same class — and a surface matching no marker fails too, since markup that moved past the sweep is how a drifted token stays invisible;
• that class is one the pinned Harmonia stylesheet really defines, read out of the codbex__harmonia webjar on the test classpath rather than restated as a literal — so a Harmonia version that renamed the token fails this test instead of quietly greying out every asterisk in the fleet.

Verified both ways: green with the fix, and red with text-destructive re-introduced into one template (my/my-form-view.html.template colours a required marker with [text-destructive] instead of text-negative).

formatter:format + formatter:validate clean on both touched modules.

Noticed, not touched

components/security/security-oauth2/src/main/resources/static/tenant-selection.html:93 uses border-destructive on the error alert — the identical defect (no such class in the Harmonia dist; the token is border-negative), on the tenant picker. Out of this issue's scope, left for its own issue.

Fixes #7155