CI optimization

[serg-temchenko]

Description

As described in the related issue #49:

Currently, our CI runner has limited resources. As a result, our CI build takes more than an hour, which is unacceptable for a healthy contribution process. To resolve this issue temporarily and focus on the current business logic, we need to simplify the CI workflow. We will improve this later by using a better instance with on-demand functionality as described in this thread.

To revert the changes made for simplification, you can execute a revert of commit ca1fce49e2f3e21a38a6a4167b15029ed856c2c0.

Also, removed toolchain installation steps, as well as Taplo and caching, since we are using a self-hosted runner where context is shared by default.

After all these changes. CI run reduced to ~36 minutes.

Important points for reviewers

CI related code should be treated as a temporary solution which should be reverted when self hosted runner will be configured.

Checklist

• Are there important points that reviewers should know?
  • If yes, which ones?
• Make sure that you described what this change does.
• If there are follow-ups, have you created issues for them?
  • If yes, which ones? / List them here: CI optimization #49
• Have you tested this solution?
• Were there any alternative implementations considered?
• Did you document new (or modified) APIs?

[jmg-duarte]

I appreciate the comments on the profile.ci, great work!