Add custom required validation text

[Magnusrm]

Adding a new customisable validation text for required validations

Added a new property, requiredValidation, to textResourceBindings, which changes the displayed validation text to be the value of properties specified text resource. If this new text resource binding is used, the old default required message is not used.

Related Issue(s)

• closes

Verification/QA

• Manual functionality testing
  • I have tested these changes manually
  • Creator of the original issue (or service owner) has been contacted for manual testing (or will be contacted when released in alpha)
  • No testing done/necessary
• Automated tests
  • Unit test(s) have been added/updated
  • Cypress E2E test(s) have been added/updated
  • No automatic tests are needed here (no functional changes/additions)
  • I want someone to help me make some tests
• UU/WCAG (follow these guidelines until we have our own)
  • I have tested with a screen reader/keyboard navigation/automated wcag validator
  • No testing done/necessary (no DOM/visual changes)
  • I want someone to help me perform accessibility testing
• User documentation @ altinn-studio-docs
  • Has been added/updated
  • No functionality has been changed/added, so no documentation is needed
  • I will do that later/have created an issue
• Changes/additions to component properties
  • Changes are reflected in both src/layout/layout.d.ts and layout.schema.v1.json, and these are all backwards-compatible
  • No changes made
• Support in Altinn Studio
  • Issue(s) created for support in Studio
  • This change/feature does not require any changes to Altinn Studio
• Sprint board
  • The original issue (or this PR itself) has been added to the Team Apps project and to the current sprint board
  • I don't have permissions to do that, please help me out
• Labels
  • I have added a kind/* label to this PR for proper release notes grouping
  • I don't have permissions to add labels, please help me out

[olemartinorg]

I don't think this works with the missingFieldsInLayoutValidations() function, and neither the validateEmptyFieldsListComponent() function. Also, I would assume it conflicts with #1281, so coordinate that with @bjosttveit.

[bjosttveit]

Yes, almost any changes to validation.ts at this point will conflict with #1281, as most of the functions and related tests are deleted. Should be straightforward to implement afterwards though.

[Magnusrm]

@bjosttveit I'll hold off on this PR until your validation refactor is completed then, and solve the merge conflict then 👍

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

0.0% Coverage
0.0% Duplication

[Magnusrm]

Closed due to weird merge conflict resolution. New PR: #1333