safty cli now reqires and account #714
Description
the CVE scanning in the CI is currently broken, as the safety check command is now deprecated.
To be able to keep using it, an account would be required and an API key needs to be added to the repo secrets.
This would also mean the CI-job can't run for PRs any longer, as they don't have access to secrets.
I disabled the job for now so CI won't fail all the time (see #713), but how do we want to procced @magmax?