Create a QA checklist document

[slifty]

We should talk with the OTS QA team to reflect on the state of the PDC framework (not just service, but our frontend, our keycloak, etc) and create a QA checklist which codifies what QA steps we have in place, what should be added, and when they should be invoked.

Next step is to reach out to Lily Ye (she's on Zulip) to start that conversation.

This came up in the context of ensuring our new Okta + Keycloak documentation stays in sync with reality over time.

[bickelj]

There are some QA steps I take when upgrading Keycloak, the most important of which is to do the login flow with SMS 2FA in the test environment before upgrading prod, then doing the same in prod after the upgrade too. These are currently documented in an infrastructure area but should be added to the general QA checklist.