Enable Nyrkiö on PRs and clickbench

[henrikingo]

• Rename push_only.yml workflow to rust_perf.yml
• Move the 'bench' task from rust.yml to rust_perf.yml
• More Nyrkio configuration options exposed:
  Team support (everyone in gh/tursodatabase can access Nyrkiö)
  Public results
  Alerting options: Comment on PR, if change detected, don't fail task
• Add Nyrkio also to analyse results from the clickbench task

[henrikingo]

You added quite a lot of benchmarks the past 2 weeks and this now takes 7 minutes or more, so I suggest to separate.

No need for Nyrkiö to do that. Just a suggestion in general.

[henrikingo]

TL;DR: Suggest to merge this version. Longer term can add support for outside contributors on the nyrkio.com side.

Ok I did some reading and there are 3 options:

• It is by design that I don't get access to any of your secrets when I'm not member of the tursodatabase team. More precisely, I think it's when I don't have write access to the repo. The first option is simply to accept this and merge this PR as it is now. For outside contributors this will exit immediately, because the Nyrkiö token is missing from the input. But it will still exit without error, so the PR looks green. (never-fail: true). If you have a PR that is expected or suspected to impact performance, you can always have a developer who has commit permission resubmit the PR and it should then run the analysis through Nyrkiö.

• It is possible to run this task in the context of the repo owner rather than the PR author. This happens if we put 'on: pull_request_target' into the top of the file. This is clearly unsafe. A variation of this would be to supply the Nyrkiö token somehow outside the secrets facility. I considered this but it too is undesirable. The way it works now anyone could login to nyrkio.com impersonating Pekka....

• I thought about it and I think it is possible for us to support / align with the github permissions model, in cases where the performance results are public. Specifically, we could change out pulls/ API so that it needs the PR author to have a Nyrkiö account, and we store the PR perf results separately in each contributors account. For the comparison we then append the PR test result to the publicly available historical results of the main branch.

• The last option would be to not run Nyrkiö at all for PRs, just post merge. This is an ok option too, if you don't like the first option in above list..

[henrikingo]

Sorry about the mess above. I accidentally pushed some different branch when I started to work on the clickbennch integration. But now everything should be good.