Renaming AddressComponent -> Address + bugfixes, improvements

[olemartinorg]

Description

• Removing StrictMode in unit tests. The reason everything rendered twice in some unit tests was that I didn't read enough about what StrictMode does, and when I saw that it purposely renders everything twice, it's obviously the cause of this problem. The profiler in the browser detects strict mode and fixes the numbers for us.
• Adding back some commented-out code in Cypress tests (should have been commented back in when validation was rewritten). Hoping it works. 🙏
• Extracting out a version compare function I implemented in Implementing an error message when backend version is outdated #1745 (thanks for the suggestion @mikaelrss, the function didn't even work correctly).
• Rewriting RepeatingGroupContext to use Zustand for the core states. This fixes a whole lot of state-keeping issues that could cause the repeating group 'add button' to disappear. I've tried adding tests for it, but wasn't able to ever reproduce it in Cypress for some reason. Still, with this rewrite it all seems to behave better.
• Renaming AddressComponent -> Address
• Slowing down the rate of requests for post places in the Address component (it mistakenly sent a request once for every letter the user typed). Added regression tests.
• Allowing null values in option lists, as per Support number, boolean and null as AppOption values app-lib-dotnet#417. I also extended the data conversion function to allow for schemas with oneOf and anyOf, as it was useful in the unit-test I wrote.

Related Issue(s)

• closes Rename AddressComponent -> Address #1495

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
• 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

[mikaelrss]

Good work! 👏 I just have some nitpicky comments 😅

[sonarqubecloud]

Quality Gate passed

The SonarCloud Quality Gate passed, but some issues were introduced.

7 New issues
0 Security Hotspots
80.3% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud