Cut 1.19.8 release

[davidnuzik]

Upstream K8s: kubernetes/sig-release#1466
K3s: k3s-io/k3s#2943

Notice:
Upstream plans to get patch releases out by 2/17/2021.

Summary:
Task covering patch release work.
Dev Complete: 2/12/2021

List of required releases:
To release as soon as able for QA:

• v1.19.8-rc1+k3s1

To release once have approval from QA:

• v1.19.8+k3s1

Prep work:

• PM: Dev and QA team to be notified of the incoming releases - send calendar invite
• PM: Dev and QA team to be notified of the date we will mark the latest release as stable - send calendar invite
• QA: Review changes and understand testing efforts
• PM: Rancher2 team notified of the release (create rancher/rancher issue and put in milestone. They will need to update rancher2 Dockerfile, etc before their next planned Rancher release) [rancherd] Bump RKE2 version - 1.18.16 rancher#30492 (comment)
• Release Captain: Prepare release notes in our private release-notes repo (submit PR for changes taking care to carefully check links and the components, once merged, create the release in GitHub and mark as a draft and check the pre-release box, fill in title, set target release branch, leave tag version blank for now until we are ready to release)
• QA: Validate and close out all issues in the release milestone.
• PM: Create an issue to mark the latest release as stable (this is done typically not later than 1 days post patch release, 7 days post new minor release) Mark v1.19.8+rke2r1 as stable #675

Vendor and release work:

• Release Captain: Tag and release any necessary RCs for QA to test KDM
• Release Captain: Tag and release when have QA approval

Post-Release work:

• Release Captain: Once release is fully complete (CI is all green and all release artifacts exist), edit the release, uncheck "Pre-release", and save.
• PM: Close the milestone in GitHub.