Update JS dependencies

[silverwind]

• Update all JS dependencies
• Added new unicorn rules
• updates now also supports updating packageManager and engines, and I see no reason not to do that, so I think we can try keeping these updated as well. If something in the build breaks because of this, I will revert and exclude pnpm from updating further, but as far as I understand, only corepack respects this field and pnpm itself does not care about it.
• Regenerate SVGs.

[silverwind]

According to https://pnpm.io/package_json#engines, pnpm does care about engines:

During local development, pnpm will always fail with an error message if its version does not match the one specified in the engines field.

So i guess I will revert this, given that some developers may run slightly older versions.

[silverwind]

So I think the best course forward is:

• Keep engines.pnpm at the minimum supported version
• Keep packageManager updated, this field is used and required by pnpm/action-setup (ref), unless we want to specify pnpm version in actions config.

I updated updates to no longer updated engines by default