Add regular software "spring clean" to blueprints

[joshwlambert]

In today's LSHTM-MRCG Epiverse catch up (2025-04-09) it was mentioned that to ensure sustainability of Epiverse-TRACE packages we should ensure that they comply with the standards outlined in the blueprints. This helps onboarding new contributors or maintainers as some of the developer knowledge is written up in the blueprints. It was mentioned that this could/should be achieved with a regular check and tidying of packages, i.e. a spring clean.

However, there is no mention of this regular review and spring cleaning of Epiverse packages in the blueprints, and it is unclear to Epiverse developers this is recommended. Therefore, adding a point to the blueprints on this should hopefully alleviate any confusion and improve the upkeep of Epiverse software with our set of best practises.

[joshwlambert]

Relevant links:

• https://www.tidyverse.org/blog/2023/06/spring-cleaning-2023/
• https://www.jumpingrivers.com/blog/spring-clean-r-package-usethis/