v0.13 release

[JavierMtzRdz]

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 main reviewers:
  brookslogan, nmdefries.
• 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).
• Styling and documentation checks. Make a PR comment with:
  • /style to check the style and fix any issues.
  • /document to check the package documentation and fix any issues.
  • /preview-docs to preview the docs.
  • See Actions GitHub tab to track progress of these commands.
• See DEVELOPMENT.md for more information on the development
  process.

Change explanations for reviewer

This PR bumps the version to 0.13.0 and updates a couple of broken links. When released on main, this unblocks epipredict. epipredict#483 restores .max_keys = Inf in autoplot.epi_workflow(), but .max_keys doesn't exist on any released epiprocess version yet. Calling it against an older epiprocess silently falls through to and tidyselect chokes on Inf ("Can't convert from Inf <double> to <integer>"). Once this merges and gets released as epiprocess 0.13.0, epipredict can pin `epiprocess (>= 0.13.0)^ in its DESCRIPTION and a normal install will pull in a compatible epiprocess automatically.

Locally verified: devtools::check() (0 errors/warnings), lintr::lint_package() (clean), styler::style_pkg() (clean).

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

• Resolves #{issue number}