Filtering support for all options-components

[olemartinorg]

Description

This adds support for filtering options via an expression. The optionFilter property allows an expression that will run for each of the available options, and will only keep the option if the expression returns true.

An example from the ttd/frontend-test test-case:

{
  "id": "ingredientType",
  "type": "Dropdown",
  "textResourceBindings": {
    "title": "Ingrediens"
  },
  "dataModelBindings": {
    "simpleBinding": "FilteredOptions.Ingredients.Type"
  },
  "optionsId": "foods",
  "optionFilter": ["and",
    // Always remove disliked foods
    ["not", ["commaContains", ["dataModel", "FilteredOptions.Dislikes"], ["value"]]],
    ["or",
      // Remove those that have been used elsewhere
      ["not", ["commaContains", ["dataModel", "FilteredOptions.UsedTypes"], ["value"]]],
      // But not if it's the currently chosen ingredient here
      ["equals", ["component", "ingredientType"], ["value"]]
    ]
  ],
  "sortOrder": "asc",
  "required": true
}

Related Issue(s)

• closes Forhindre gjenbruk av innhold i dropdownliste på tvers av rader i repeterende tabell #1971

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
    • Cleaning up and adding lots of docs about options (code lists / svaralternativer) altinn-studio-docs#1934
  • No functionality has been changed/added, so no documentation is needed
  • I will do that later/have created an issue
• 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

[sonarqubecloud]

Quality Gate passed

Issues
1 New issue
0 Accepted issues

Measures
0 Security Hotspots
88.9% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[paal2707]

Ser bra ut! :)