1.3.4 Release check list

[seabbs]

• Get passing CRAN checks
• @sbfnk review develop.
• @seabbs make any final changes required to Develop #343.
• Merge in Develop #343.
• @seabbs kick the tires on main.
• @sbfnk kick the tires on main.
• Make a decision about the severity of estimate_secondary prevalence model does not recover the synthetic parameters #349
• check_rhub() on all platforms.
• check_win_devel() (in progress).
• Review news (@sbfnk).
• Update cran-comments.md (@seabbs).
• Release to CRAN.
• Navigate release through CRAN
• Tag release.
• Bump development version.
• Tweet/Toot.

The only outstanding issue I haven't dealt with flagged by CRAN is the long running examples. Their complaint was that all examples (including those flagged as don't test) took over 3 hours on their machine and that this was ridiculous. Given that 1. it only takes an hour in our CI and 2. it isn't like a user runs every example I am minded to take no action and hope they don't flag it again (it only came up because we were arguing about if the package writes to the users directory and some point scoring was needed).