Ndefries/epidatasets migration

[nmdefries]

Checklist

Please:

• Make sure this PR is against "dev", not "main".
• Request a review from one of the current epipredict main reviewers:
  dajmcdon.
• Make sure to bump the version number in DESCRIPTION and NEWS.md.
  Always increment the patch version number (the third number), unless you are
  making a release PR from dev to main, in which case increment the minor
  version number (the second number).
• Describe changes made in NEWS.md, making sure breaking changes
  (backwards-incompatible changes to the documented interface) are noted.
  Collect the changes under the next release number (e.g. if you are on
  0.7.2, then write your changes under the 0.8 heading).
• Consider pinning the epiprocess version in the DESCRIPTION file if
  • You anticipate breaking changes in epiprocess soon
  • You want to co-develop features in epipredict and epiprocess

Change explanations for reviewer

Moves included datasets to the epidatasets package. Some datasets are being used by epiprocess as well, so dataset names change. The data are reexported in epipredict for easy access. Data contents mostly remain the same. The exception is that the Canadian graduate salary dataset now has values for 2017.

[nmdefries]

@dajmcdon Any suggestions on the tests failures? There are also a bunch of warnings about adding new snapshots. The tests pass locally for me.

[dajmcdon]

How are you running them locally? You may have to push changes to those files.

[nmdefries]

I'm doing rcmdcheck::rcmdcheck() in Rstudio. It doesn't seem to be making new snapshots...

[dajmcdon]

Can you try devtools::test()? It should hopefully produce the same snapshot mistakes. Otherwise, perhaps @dsweber2 can help.

[nmdefries]

devtools::test() output is a much closer match, thanks!

[brookslogan]

This makes document() run very slowly on my system. profvis with default interval crashes my computer; with interval = 1 gives a bunch of time in warn_missing_s3_exports though I don't think I saw any emitted warnings. (Though I felt see some sort of complaints when documenting before it started taking 8 minutes.)

[nmdefries]

@brookslogan Documenting runs faster for me now. Is it working better for you?