Improve our navigation buttons (Next and back)

[Febakke]

Description

Today we have two primary buttons for next and back. We should change this so that we follow our own guidelines on how you use the button component from the design system.

Relevant article from Aksel

Screenshots

Link to Figma

Considerations

This is needed to solve other issues in the backlog.

Ops requirements

Acceptance criteria

Describe criteria here (i.e. What is allowed/not allowed (negative tesing), validations, error messages and warnings etc.)

Specification tasks

• [x] Design secondary button

Development tasks

• [ ] Create secondary button

Test

Add test cases here as checkboxes that are being tested as part of the changes.

Definition of done

Verify that this issue meets DoD (Only for project members) before closing.

• [ ] Documentation is updated (if relevant)
  • [ ] Technical documentation (docs.altinn.studio)
  • [ ] User documentation (altinn.github.io/docs)
• [ ] QA
• [ ] Manual test is complete (if relevant)
• [ ] Automated test is implemented (if relevant)
• [ ] All tasks in this userstory are closed (i.e. remaining tasks are moved to other user stories or marked obsolete)

[mrosvik]

We did some changes to the "Button" component in Figma after merging with Altinn and Digdir's design system. I have updated the link in the issue to the latest sketches. @mjulstein