Check if storage should be updated during invalidation

[elliesterner]

Description

The move command vault secrets move kv1 kv2 and vault auth move userpass1 userpass2 calls the sys/remount endpoint, which always gets forwarded to the active node. If performance standbys are present in the cluster, they will attempt to write to storage during invalidation. This PR makes sure that perf standbys don't write to storage, to avoid the logical.ErrReadOnly error.

ENT PR
JIRA

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! ✅

[biazmoreira]

Would you like me to wait until the tests are fixed to review it?

[elliesterner]

Would you like me to wait until the tests are fixed to review it?

My bad! These tests should be in ENT only. I'll pull them out.

[mpalmi]

LGTM 🚀