audit: Fix missing request ID in audit log for help operations

[Flamefire]

The handleHelp function in http/help.go didn't set an ID unlike all other handlers.
This caused the request.id field to be silently omitted from audit log entries for all
help operations (e.g. vault path-help), making it impossible to correlate request and response entries in the audit log.

Fix this by setting that ID

Fixes #32026

[vercel]

Deployment failed with the following error:

The `vercel.json` schema validation failed with the following message: should NOT have additional property `public`

Learn More: https://vercel.com/docs/concepts/projects/project-configuration

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
vault-ui	Error		Jul 10, 2026 6:58am

[hashicorp-cla-app]

All committers have signed the CLA.

[hashicorp-cla-app]

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

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

[heatherezell]

Hi there! Thanks for this fix. Please sign the CLA and ping me when that's done, so I can get this in front of engineers for review. :)

[Flamefire]

@heatherezell Thought that went through already, done now

[heatherezell]

@Flamefire It looks like you might have submitted a commit from either email or something else that GitHub doesn't see as connected to your GitHub account - can you take a peek?

[Flamefire]

What exactly are you referring to? All commits have the same email and all are with a GitHub registered email and shown as mine.
Anyway, I rebased to main to retrigger all checks and at least that CLA CI check is green, but that one has been green before.
Let me know if there is anything else that I might have missed