Backport of api/seal-status: fix deadlock when namespace is set on seal-status calls into release/1.13.x

[hc-github-team-secure-vault-core]

Backport

This PR is auto-generated from #23861 to be assessed for backporting due to the inclusion of the label backport/1.13.x.

🚨

Warning automatic cherry-pick of commits failed. If the first commit failed,
you will see a blank no-op commit below. If at least one commit succeeded, you
will see the cherry-picked commits up to, not including, the commit where
the merge conflict occurred.

The person who merged in the original PR is:
@jasonodonnell
This person should manually cherry-pick the original PR into a new backport PR,
and close this one when the manual backport PR is merged in.

merge conflict error: POST https://api.github.com/repos/hashicorp/vault/merges: 409 Merge conflict []

The below text is copied from the body of the original PR.

---

PR #10725 introduced a change to support namespaces in vault status requests but introduced a deadlock on calls to sys/seal-status when namespaces are included.

When requests have a namespace configured the handler routes the request through switchedLockHandleRequest and holds the read statelock for the duration of the request:

vault/vault/request_handling.go

Lines 530 to 533 in 550c99a

	if doLocking {
	c.stateLock.RLock()
	defer c.stateLock.RUnlock()
	}

.

I've added a locking arg so the caller can decide if the statelock needs to be grabbed or not.

---

Overview of commits

• 29d8929

[hashicorp-cla]

All committers have signed the CLA.

[github-actions]

Build Results:
All builds succeeded! ✅

[github-actions]

CI Results:
All Go tests succeeded! ✅