ci: add docs preview

[dshemetov]

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

Adds /preview-docs command to help with docs review

Magic GitHub syntax to mark associated Issue(s) as resolved when this is merged into the default branch

• Resolves #{issue number}

[dajmcdon]

@dshemetov Apologies for my bone-headedness, but how would you suggest that I review this PR? What should I look at?

[dshemetov]

Well, I suppose it's hard to test without merging into main and trying out the workflow. Otherwise you can see here where I tested it. When one of us comments /preview-docs an action is fired and eventually the bot will give a link to a hosted version of the docs.