Cypress: New tools/functions

[olemartinorg]

Description

I'm porting these over from feat/grid and feat/components-in-table early, because those branches are blocked by changes in the design system we're waiting for, and these tools come in handy now.

Two new functions have been added:

• cy.navPage(name) lets you get the button for navigating to a specific page, by a given name. So cy.navPage('form').click() will click the navigation button for 1. form (the first page in the changename task in frontend-test).
• cy.changeLayout() lets you change the current layout configuration without reloading the page (using the same trick as the developer tools is using). This might not always be what you want, since some effects of the layout configuration runs in sagas when the app is loading.

Related Issue(s)

• closes #{issue number}

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]

@bjosttveit Thought these might be useful if you're writing tests for #1106 (especially if you're adding a new page, which is why I made the first tool - since I'm adding a new page for feat/grid as well).

[bjosttveit]

Very cool