CI Fixes And Refactor

[wereii]

• I have split the checks (format, lint, future tests) from build so that it runs once and only on linux as windows in CI is painful. As long as the npm steps and CI is alright it should :tm: work even if windows is not covered, it also speeds it up because GA Windows is some slow 2016 server. Like this it should also be possible to run checks for pull requests without building.
• the ~setup-node~ action installs very old npm by default (for node 14, using nvm use on Linux I get v9.6.7 by default) so I have added a step that pulls the latest npm, this fixes errors like cipm can only install packages when your package.json and package-lock.json or npm-shrinkwrap.json are in sync ... or Cannot read property '@iconify-icons/mdi' of undefined which happens when newer npm generates the package lock
• Fixed prettier runs by quoting the paths - (linux) shellnanigans - depending on the running shell it could expand the paths beforehand and skip some files that prettier itself would not skip

[wereii]

Please try running fix, dev and build on your machine before accepting

I am developing on Linux and I am not sure if the changes to prettier will work on windows

[wereii]

• the new release script in package.json is important as it tells electron-builder to absolutely definitely do a github release https://www.electron.build/configuration/publish#how-to-publish, it should also check if there is draft release and add built files into it, otherwise it will create draft release for that tag (tested)
• tests have been extended with npm build to check that vite can build it (for electron)

The main differences to current CI

• tests (type check, format, lint) are run only on linux host, for speed ups
• split tests and build to run on different events - build will run only for tags, the idea here is that the final building shouldn't be affected by code (src/) changes, for testing electron versions and configuration changes I could should add manual trigger~~ Note: build & release process is now started by simply tagging and does not depend on the results of tests - it is possible to release with commit(s) that did not pass tests (could be dangerous, might be useful), thought this can only happen if new commit and new tag are pushed in quick succession (eg. before tests have time to finish)
• removed the unmaintained samuelmeuli/action-electron-builder action and replaced with the electron-builder itself for publishing/releases
• Added manual trigger for build step - so that changes to the build steps (electron configuration or version changes) can be tested too.
  Note: Though what I don't like about this is that triggering a workflow manually on a branch does not seem to link the results with any PRs or commit directly and the run is only visible in Actions tab so it's hard to track, quick google search says this could be replaced with custom Actions Environment that requires manual approval to run

I am sorry this might be a lot but I just kept going:)