Repo: clean up and add npm workspaces

Which issue does this PR close?

This PR closes #3409 closes #3410

What is the new behavior?

In this PR I have:

Cleaned up some unused files from old deployment setups etc.
Cleaned up unused scripts, mainly nx related stuff
Added npm workspaces to support better separation between code and dependencies
- In addition to the existing libs and apps, I have also added our eslint config and some of the tools-scripts to their own workspaces
Added the core package as an nx project so building and linting is managed and cached alongside the other projects
Run common tasks across workspaces with nx

Some future work might include adding a shared tsconfig, similar to how we do it for the eslint config, but it requires a bit more thought to streamline the typescript options without breaking the outputted code, so I think it should be handled seperately.

Does this PR introduce a breaking change?

[ ] Yes
[x] No

Are there any additional context?

Checklist:

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

Reminders

[ ] ~~Make sure you have implemented tests following the guidelines in: "The good: Test".~~
[ ] ~~Make sure you have updated the cookbook with examples and showcases (for bug fixes, enhancements & new components).~~

Review

[x] Determine if your changes are a fix, feature or breaking-change, and add the matching label to your PR. If it is tooling, dependency updates or similar, add ignore-for-release.
[x] Do a self-review.
[x] Request that the changes are code-reviewed
[ ] ~~Request that the changes are UX reviewed (only necessary if your PR introduces visual changes)~~

When the pull request has been approved it will be merged to develop by Team Kirby.

kirbydesign / designsystem