ci: fix pkgdown

[dshemetov]

Checklist

Please:

• Make sure this PR is against "dev", not "main" (unless this is a release
  PR).
• Request a review from one of the current epidatr main reviewers:
  brookslogan, dshemetov, nmdefries, dsweber2.
• Makes sure to bump the version number in DESCRIPTION. 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
  1.7.2, then write your changes under the 1.8 heading).

Change explanations for reviewer

CI seems to be misbehaving and we're getting the dev branch docs on the main page. Try to fix with Github variables instead of contexts.

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

• Resolves #{issue number}

[dshemetov]

Do we need this, if we're overwriting whenever we build pages?

[dsweber2]

I was mostly just trying to be explicit about the default