ci: use semantic-release

[dargmuesli]

• merges lint and test jobs into a single ci job to save some resources on duplicate initialization at the cost of less parallelization, which is reasonable I think (can be reverted if there are any other reasons to have the jobs split)
• adds cycjimmy/semantic-release-action using the conventionalcommits preset (! marks breaking changes, which is not the case with the default angular preset)

The PERSONAL_ACCESS_TOKEN secret could be set to a value owned by https://github.com/nuxtbot maybe, which could then be muted by anyone who does not wish to receive notifications for every automated release (which can happen quite often by design).

Could well be that some issue, like possibly a requirement to set PERSONAL_ACCESS_TOKEN, arises once merged because the release action does its full cycle only then. I'll of course monitor that on merge and fix everything related, like updating the required status checks.

[codecov[bot]]

Codecov Report

Merging #277 (00b5fbf) into main (2450b17) will not change coverage. The diff coverage is n/a.

:exclamation: Current head 00b5fbf differs from pull request most recent head a8dd060. Consider uploading reports for the commit a8dd060 to get more accurate results

@@           Coverage Diff           @@
##             main     #277   +/-   ##
=======================================
  Coverage   82.60%   82.60%           
=======================================
  Files           2        2           
  Lines         115      115           
  Branches       13       13           
=======================================
  Hits           95       95           
  Misses         20       20           

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more