VAULT-28192 Add known issue for Agent/Proxy CPU issue

[VioletHynes]

Description

This adds a known issue for the issue fixed by #27518 and described by VAULT-28192.

As per guidance, I added versions to all of the Changes as opposed to adding a new Versions column.

TODO only if you're a HashiCorp employee

• Labels: If this PR is the CE portion of an ENT change, and that ENT change is
  getting backported to N-2, use the new style backport/ent/x.x.x+ent labels
  instead of the old style backport/x.x.x labels.
• Labels: If this PR is a CE only change, it can only be backported to N, so use
  the normal backport/x.x.x label (there should be only 1).
• 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! ✅

[VioletHynes]

I'm happy to remove or adjust this column if necessary, it just felt like the right way to indicate that this was 1.17.0 only and will be fixed in the next version. Let me know what you think or if there's another approach you'd prefer I take for such an issue.

It can be viewed here: https://vault-54m6izb8b-hashicorp.vercel.app/vault/docs/release-notes/1.17.0