CI: only keep conda cache for one day
Our conda envs are being cached, but that also means that for the dev builds (eg numpy nightly, pyarrow nightly), you don't actually get the latest version, depending on whether some other change happened in the CI setup that would invalidate the cache.

Maybe ideally we do this _only_ for those builds that test for other dev packages? 

From https://github.com/mamba-org/setup-micromamba?tab=readme-ov-file#caching  
Related issue: https://github.com/mamba-org/setup-micromamba/issues/50
I would also support invalidating all caches daily (the pre-commit caches I think are the only ones that are not affected by changing the conda key). You could update this workflow's cron to daily (and rename the file) https://github.com/pandas-dev/pandas/blob/main/.github/workflows/cache-cleanup-weekly.yml  This pull request is stale because it has been open for thirty days with no activity. Please [update](https://pandas.pydata.org/pandas-docs/stable/development/contributing.html#updating-your-pull-request) and respond to this comment if you're still interested in working on this. This got implemented in https://github.com/pandas-dev/pandas/pull/58710 (thanks for the inspiration!) so closing