Add to news closed issues

[bailliem]

What changes are proposed in this pull request?

Review and complete the updates to the News.md file since prior release.
Updates to README ahead of release.
TODO: Do we need a pkgdown badge on the README (and subsequently the website)?

Which files are involved in this pull request and what changes were made?

N/A

Did you include unit tests for the proposed change/bug fix (https://testthat.r-lib.org/)?

N/A

If there is an GitHub issue associated with this pull request, please provide link.

closes #420
closes #424

---

Checklist for PR reviewer

• PR branch has pulled the most recent updates from main branch. Ensure the pull request branch and your local version match and both have the latest updates from the main branch.
• If a new function was added, function should be included in _pkgdown.yml
• If a bug was fixed, a unit test was added for the bug check
• Run pkgdown::build_site(). Check the R console for errors, and review the rendered website.
• Code coverage is suitable for any new functions/features. Review coverage with withr::with_envvar(new = c("NOT_CRAN" = "true"), covr::report()). Before you run, begin a fresh R session without any packages loaded.
• R CMD Check runs without errors, warnings, and notes
• usethis::use_spell_check() runs with no spelling errors in documentation
• Has NEWS.md been updated with the changes from this pull request under the heading indicating the latest version. If there is an issue associated with the pull request, reference it in parentheses at the end update (see NEWS.md for examples).
• Has the version number been incremented using usethis::use_version(which = "dev")
• Run devtools::build_readme() to build the README.md file.
• Approve Pull Request
• Merge the PR. Please use "Squash and merge".

[SHAESEN2]

Should we run the tests of Tim (watchdog) for CRAN release?

[bailliem]

Should we run the tests of Tim (watchdog) for CRAN release?

I'll look in to it and run it prior to submission

[ddsjoberg]

almost there!