Add helpButton/helpPanel to admin CRUD forms

[johlju]

Summary

Migrate admin CRUD forms to use the helpButton / helpPanel pattern already established in RequirementFormFields.tsx and NormReferenceFormFields.tsx.

Background

The requirement form and norm-reference form provide inline contextual help via helpButton(field, label) and AnimatedHelpPanel. None of the simpler admin CRUD pages currently use this pattern, which creates an inconsistent UX between requirement editing and taxonomy management.

Scope

Add helpButton / helpPanel support to these admin CRUD forms:

• app/[locale]/package-item-statuses/package-item-statuses-client.tsx
• app/[locale]/requirement-statuses/requirement-statuses-client.tsx
• app/[locale]/requirement-areas/requirement-areas-client.tsx
• app/[locale]/owners/owners-client.tsx
• app/[locale]/quality-characteristics/quality-characteristics-client.tsx
• app/[locale]/usage-scenarios/usage-scenarios-client.tsx
• app/[locale]/norm-references/norm-references-client.tsx
• app/[locale]/requirement-packages/responsibility-areas/responsibility-areas-client.tsx
• app/[locale]/requirement-packages/implementation-types/implementation-types-client.tsx

Tasks

• Decide which fields on each form genuinely benefit from contextual help (not every field needs it)
• Create translation keys in messages/en.json and messages/sv.json for the help text
• Extract a shared helper or pattern so all admin forms use the same approach
• Add unit tests for help panel toggling on at least one representative form
• Apply consistently across all listed forms

Why plan separately

Implementing this on just one or two forms would create a patchwork UX. The migration should be designed holistically so the help experience is uniform across all admin pages.

[johlju]

Field-level suggestions from code review

These details came from an AI code review that was validated — adding them here as implementation notes for the two forms that were specifically called out.

owners-client.tsx

Fields to consider: firstName, lastName, email

Suggested translation keys:

• owners.firstName.help
• owners.lastName.help
• owners.email.help

requirement-areas-client.tsx

Fields to consider: prefix, name, description, owner

Suggested translation keys:

• requirementAreas.prefix.help
• requirementAreas.name.help
• requirementAreas.description.help
• requirementAreas.owner.help

Pattern reference

Use the same helpButton() / helpPanel() / AnimatedHelpPanel / toggleHelp state pattern from RequirementFormFields.tsx (around line 222–253). Each form will need a local openHelp set + toggleHelp function, and matching keys in both messages/en.json and messages/sv.json.