feat: use self-hosted runner

[cernicc]

Use our own self hosted runner by choosing it when defining a ci job.

[jmg-duarte]

LGTM but I'm not sure we need to keep the setup steps.

We can setup the environment and save time there.

[th7nder]

How did we test that? I suppose it was configured in the repo settings somehwere (with credentials and all of that)?

[cernicc]

Yeah. It's not hard to set it up. they give you everything basically. But you can't test it in advance. We will see if the next job will be pushed to the runner. We are currently running ci only on main, develop and tagged PRs

More: https://docs.github.com/en/actions/hosting-your-own-runners/managing-self-hosted-runners/adding-self-hosted-runners

[th7nder]

LGTM

[serg-temchenko]

Looks good, but this PR made me to create this issue #40. 😅

[serg-temchenko]

I've added needs options to the format and clippy_build_and_test jobs to ensure all jobs execute in sequence. This makes the TOML linter and formatter run first and fail if any issues are found before running clippy_build_and_test. Before these changes, I noticed that clippy_build_and_test was running first, which is not optimal.

I also tested running Clippy after cargo build since I remember that it uses build components and should improve the execution speed. However, tests showed that this is not true as of now; perhaps some changes were made.

[cernicc]

Looks good, but this PR made me to create this issue #40. 😅

Nice :D My laziness already improving the processes :D

[serg-temchenko]

Just leaving this here.

Moving Clippy to the end of builds increased the runtime by ~15 minutes.