Backport of Add directory paths to KV capabilities checks into release/1.15.x

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

Backport

This PR is auto-generated from #24404 to be assessed for backporting due to the inclusion of the label backport/1.15.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:
@Monkeychip
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.

---

Fixes Issue #24130

Follow the instructions from the original issue to duplicate. The bug occurred because we were passing in path to the capabilities check but path does not include the full path name.

Ex: for secret beep/bop/boop
We would always pass in boop even if we were searching for the list return of beep/bop/
Now we pass in beep/ or beep/bop/ or beep/bop/bop depending on the path in the URL for the view.

Screenshots using the policy on the issue
Before:

After:

---

Overview of commits

• 85acabb

[hashicorp-cla]

Thank you for your submission! We require that all contributors sign our Contributor License Agreement ("CLA") before we can accept the contribution. Read and sign the agreement

Learn more about why HashiCorp requires a CLA and what the CLA includes

---

temp seems not to be a GitHub user.
You need a GitHub account to be able to sign the CLA. If you already have a GitHub account, please add the email address used for this commit to your account.

_{Have you signed the CLA already but the status is still pending? Recheck it.}

[github-actions]

CI Results:
All Go tests succeeded! ✅