[Enhancement] Convert all Kirby Components to standalone components

[Fuzzy3]

Describe the enhancement

The Kirby Design System should follow the recent convention from angular and convert all of its components to standalone components. This will provide much more flexibility since consumers may then be much more specific in what components they want to import rather than importing the huge all-in-one KirbyModule.

Describe the solution you'd like

Make all or most components in the KirbyModule standalone.

Have you considered any alternatives?

Do nothing now and wait until the components are converted to CustomElements.

Are there any additional context?

Might give a better workaround for the problem in this: #3742

---

Checklist:

The following tasks should be carried out in sequence in order to follow the process of contributing correctly.

Refinement

• Request that the issue is UX refined
• Request that the issue is tech refined; do not proceed until this is done.

Implementation

The contributor who wants to implement this issue should:

• Make sure you have read: "Before you get coding".
• Signal to others you are working on the issue by assigning yourself.
• Create a branch from the develop branch following our branch naming convention.
• Publish a WIP implementation to Github as a draft PR and ask for feedback.
• Make sure you have implemented tests following the guidelines in: "The good: Test".
• Update the cookbook with examples and showcases.

Review

Once the issue has been implemented and is ready for review:

• Do a self-review.
• Create a pull-request. If you created a draft PR during implementation you can just mark that as "ready for review".