Release `1.2.0` process

[dsweber2]

• [x] git pull on dev branch.
• [x] Make sure all changes are committed and pushed.
• [x] Check current CRAN check results.
• [x] devtools::check(".", manual = TRUE, env_vars = c(NOT_CRAN = "false")).
  • Aim for 10/10, no notes.
• [x] If check works well enough, merge to main. Otherwise open a PR to fix up.
• [x] Polish NEWS.
  • Some guidelines.
• [x] git checkout main
• [x] git pull
• [x] urlchecker::url_check().
  • This may choke on the MIT license url, and that's ok.
• [x] devtools::build_readme()
• [x] devtools::check_win_devel()
• [x] Have maintainer ("cre" in description) check email for problems.
• [x] revdepcheck::revdep_check(num_workers = 4).
  • This may choke, it is very sensitive to the binary versions of packages on a given system. Either bypass or ask someone else to run it if you're concerned.
• [x] Update cran-comments.md
• [x] PR with any changes (and go through the list again) into dev and run through the list again.

Submit to CRAN:

• [x] devtools::submit_cran().
• [x] Maintainer approves email.

Wait for CRAN...

• [x] If accepted :tada:, move to next steps. If rejected, fix and resubmit.
• [x] Open and merge a PR containing any updates made to main back to dev.
• [x] usethis::use_github_release(publish = FALSE) (publish off, otherwise it won't push) will create a draft release based on the commit hash in CRAN-SUBMISSION and push a tag to the GitHub repo.
• [x] Go to the repo, verify the release notes, and publish when ready.