Noting auto-check failures

[pbulsink]

It looks like there's some auto-check failures from reticulate/uv, or even at base. This corresponds with uv and reticulate updates in the last two weeks. For now I'll just monitor this and see if it resolves with further package updates, or if we need to modify testing code to fix.

── Warning ('test-clear_f1_cache.R:22:3'): Cache Clearing works for memoised functions to file ──
running command ''/home/runner/.cache/R/reticulate/uv/cache/archive-v0/k_JCX9S7X7Xzsrh14kmd_/bin/python' -m pip freeze' had status 1
Backtrace:
    ▆
 1. └─f1dataR::clear_f1_cache() at test-clear_f1_cache.R:22:3
 2.   ├─"fastf1" %in% reticulate::py_list_packages()$package at f1dataR/R/clear_f1_cache.R:19:5
 3.   └─reticulate::py_list_packages() at f1dataR/R/clear_f1_cache.R:19:5
 4.     └─reticulate:::pip_freeze(python) at reticulate/R/install.R:261:3
 5.       └─base::system2(python, args, stdout = TRUE) at reticulate/R/pip.R:97:3

[pbulsink]

Specifically see the failures here: https://github.com/SCasanova/f1dataR/actions/runs/19022513964