Implement basic Link component + use it in the docs

[larsrickert]

Replace the docs typography: link section with a OnyxLink component.

Why?

The typography preview currently only shows style without having a OnyxLink component in use here which was added in #211. To make sure that we won't diverge with the typography docs and a future link component, we want to create the basic link already now.

Design

Figma

Acceptance criteria

• The link component
  • [x] has a label (which can be marked), and it is a slot.
  • [x] can be clicked via mouse or keyboard
  • [x] make href required
  • [x] for now: does not support file type, or icon examples in storybook
• [x] OnyxLink is used in docs typography: link section

Definition of Done

• [x] covered by component tests
• [x] screenshot tests are updated
• [x] updated version + documentation is deployed
• [x] Storybook can show the feature
• [x] Set task to In review

Review

• Storybook link
• [x] approved by designer @mj-hof
• [x] approved by dev @BoppLi

Implementation details

• OnyxLink
  • stay close to the <a>-tag: MDN Link
  • offer a property target. if blank is selected, preset rel="noreferrer" on the <a>-tag, see MDN docs and this article for background info
• relevant component in the docs is: apps/docs/src/.vitepress/components/OnyxTypography.vue

Reference implementations

• CoreUI

Applicable ARIA Pattern

Aria Link

[larsrickert]

Headline is already done in #236

[BoppLi]

could you modify the grammar in the storybook text?

Links are a navigational elements that direct users to other pages, whether they are internal or external.

-> remove the "a": `Links are navigational elements

[BoppLi]

see ticket implementation details: only noreferrer, it includes the noopener