Updates for packages incoming (admiral, xportr, metatools, metacore)

[bms63]

Be good to make sure development versions of these packages don't impact the site.

I'll try to take for a spin, but if others have time please jump on in and see how the development versions of the packages are shaping up. @pharmaverse/examples

Actually, @pawelru is there a way to run a monthly test to see if the site builds without errors with the development versions of all the packages that we use? SO if site errors we get a message, if no error then no message.

[pawelru]

We already have a mini tool for this: https://github.com/insightsengineering/setup-r-dependencies. It's a wrapper of r-lib/actions/setup-r-dependencies that has a special lookup-refs parameter. If provided, it would add Config/Needs/... field to the DESCRIPTION file with pak-friendly github refs of predefined set of dependencies (not necessarily all of them) and then use it when installing deps. The bad thing is that this is a non-standard data stored in the github actions config file so every time we add a new dependencies (that are in the scope of such testing) - we would have to add there as well.

Such prod / dev deps should work well. We would still have to run this on schedule and setup automation on error.