[docs] add known issue where static roles get rotated on upgrade

[elliesterner]

Description

What does this PR do?

TODO only if you're a HashiCorp employee

• Backport Labels: If this fix needs to be backported, use the appropriate backport/ label that matches the desired release branch. Note that in the CE repo, the latest release branch will look like backport/x.x.x, but older release branches will be backport/ent/x.x.x+ent.
  • LTS: If this fixes a critical security vulnerability or severity 1 bug, it will also need to be backported to the current LTS versions of Vault. To ensure this, use all available enterprise labels.
• ENT Breakage: If this PR either 1) removes a public function OR 2) changes the signature
  of a public function, even if that change is in a CE file, double check that
  applying the patch for this PR to the ENT repo and running tests doesn't
  break any tests. Sometimes ENT only tests rely on public functions in CE
  files.
• Jira: If this change has an associated Jira, it's referenced either
  in the PR description, commit message, or branch name.
• RFC: If this change has an associated RFC, please link it in the description.
• ENT PR: If this change has an associated ENT PR, please link it in the
  description. Also, make sure the changelog is in this PR, not in your ENT PR.

[github-actions]

CI Results:
All Go tests succeeded! ✅

[github-actions]

Build Results:
All builds succeeded! ✅

[anwittin]

Looks good thanks Ellie!

[schavis]

FYI, updating the older release notes (release-notes/1.16.1, release-notes/1.17.0, release-notes/1.18.0) and upgrade pages (upgrade-to-1.16.x, upgrade-to-1.16.x, upgrade-to-1.17.x, upgrade-to-1.18.x) won't correctly update the versioned docs for those releases. You'll need to make those updates under the relevant release branch (release/1.16.x for the 1.16.x updates, release/1.17.x for the 1.17.x updates, and release/1.18.x for the 1.18.x updates).

[elliesterner]

FYI, updating the older release notes (release-notes/1.16.1, release-notes/1.17.0, release-notes/1.18.0) and upgrade pages (upgrade-to-1.16.x, upgrade-to-1.16.x, upgrade-to-1.17.x, upgrade-to-1.18.x) won't correctly update the versioned docs for those releases. You'll need to make those updates under the relevant release branch (release/1.16.x for the 1.16.x updates, release/1.17.x for the 1.17.x updates, and release/1.18.x for the 1.18.x updates).

Thanks @schavis . I plan to backport those once this one get's merged, so I can just grab the one commit.