update renv files locally

[avallecam]

this is to make the project run with R 4.4.0 and the latest packages

to do this we followed steps listed in epiverse-trace/tutorials#75

---

After update issues to fix:

Fix #40

[github-actions]

Thank you!

Thank you for your pull request 😃

🤖 This automated message can help you check the rendered files in your submission for clarity. If you have any questions, please feel free to open an issue in {sandpaper}.

If you have files that automatically render output (e.g. R Markdown), then you should check for the following:

• 🎯 correct output
• 🖼️ correct figures
• ❓ new warnings
• ‼️ new errors

Rendered Changes

🔍 Inspect the changes: https://github.com/epiverse-trace/tutorials-late/compare/md-outputs..md-outputs-PR-39

The following changes were observed in the rendered markdown documents:

 compare-interventions.md                           |   16 +-
 config.yaml (gone)                                 |   83 -
 fig/model-choices-rendered-unnamed-chunk-3-1.png   |  Bin 18391 -> 15163 bytes
 fig/model-choices-rendered-unnamed-chunk-4-1.png   |  Bin 9234 -> 9223 bytes
 ...ing-interventions-rendered-plot_vaccinate-1.png |  Bin 36227 -> 36261 bytes
 fig/simulating-transmission-rendered-traj-1.png    |  Bin 46264 -> 46251 bytes
 md5sum.txt                                         |   28 +-
 model-choices.md                                   |   53 +-
 modelling-interventions.md                         |   34 +-
 renv.lock (gone)                                   | 1796 --------------------
 simulating-transmission.md                         |   60 +-
 11 files changed, 88 insertions(+), 1982 deletions(-)

What does this mean?

If you have source files that require output and figures to be generated (e.g. R Markdown), then it is important to make sure the generated figures and output are reproducible.

This output provides a way for you to inspect the output in a diff-friendly manner so that it's easy to see the changes that occur due to new software versions or randomisation.

⏱️ Updated at 2024-06-11 19:27:13 +0000

[avallecam]

From md-outputs, we identified an unexpected change given updates in {epidemics}, filled as an issue in #40 , now fixed in c3c3704