Release epichains 0.1.0

[jamesmbaazam]

First release:

• Proofread Title: and Description:
• Acknowledge all contributors/contributions
• Check that all exported functions have @return and @examples
• Check that Authors@R: includes a copyright holder (role 'cph')
• Check licensing of included files
• Review https://github.com/DavisVaughan/extrachecks

Prepare for release:

• git pull
• Close v0.1.0 milestone
• urlchecker::url_check()
• devtools::build_readme()
• devtools::check(remote = TRUE, manual = TRUE)
• devtools::check_win_devel()
• git push
• Make sure links to GitHub repository and issue tracker are listed: usethis::use_github_links()
• Re-order and standardize DESCRIPTION with desc::desc_normalize()
• Organise NEWS.md file
• Run goodpractice::gp()
• Review WORDLIST
• Check if # nolint comments are still needed with recent lintr releases
• Draft blog post

Release on GitHub:

• usethis::use_version('minor')
• usethis::use_github_release()
• usethis::use_dev_version(push = TRUE)

Post release

• Add package to the Epiverse-TRACE R Universe database of packages
• Retire bpmodels and signpost to epichains

[jamesmbaazam]

Wrong option. Closing!

[jamesmbaazam]

This list was created with usethis::use_release_issue() but is a list for releasing to CRAN.
There's no usethis function to create a GitHub release, so I'll perform the actions that are not CRAN related.

[jamesmbaazam]

To be completed after #213 is merged and #156 is completed.