feat: add an option to choose between staged-dependencies and setup-r-dependencies

[walkowif]

Example of workflows adapted to select setup-r-dependencies as the dependency installation method:

• check.yaml
• docs.yaml
• release.yaml

[github-actions]

Unit Tests Summary

3 tests   3 ✅  6s ⏱️
3 suites  0 💤
1 files    0 ❌

Results for commit bbaf1eb.

♻️ This comment has been updated with latest results.

[pawelru]

This all is awesome right now. I have one more comment that would help to speed up the things - is to use PPM instead of default CRAN. This would allow us to install from binaries as opposed to download sourced - build binary - install. The difference will be significant.
Unfortunately, this is not a parameter of the setup-r-dependency action (it is in the setup-r which is meant to be run before but we are not using it currently). There should be many ways of doing this (maybe env var? or .Rprofile?). I would ask you to research this and suggest the best option.

---

UPDATE:
We can also add this to our setup-r-dependencies action as well. Up to you where you consider the most suitable place

[walkowif]

I suggested a solution for using the binary packages from PPM in insightsengineering/setup-r-dependencies#6.

[walkowif]

This PR is still used for testing insightsengineering/setup-r-dependencies#8. Once it's merged and new setup-r-dependencies action version is released

uses: insightsengineering/setup-r-dependencies@setup-binary-package-repository-for-different-platform

can be replaced with

uses: insightsengineering/setup-r-dependencies@v1

and this PR can be merged.

Edit: this is done.

[pawelru]

This looks good from my end 👍