chore: [CLI-936] Fix bugs from previous update-docs commit

[dotkas]

Pull Request Submission Checklist

• Follows CONTRIBUTING guidelines
• Commit messages
  are release-note ready, emphasizing
  what was changed, not how.
• Includes detailed description of changes
• Contains risk assessment (Low | Medium | High)
• Highlights breaking API changes (if applicable)
• Links to automated tests covering new functionality
• Includes manual testing instructions (if necessary)
• Updates relevant GitBook documentation (PR link: ___)
• Includes product update to be announced in the next stable release notes

What does this PR do?

Fixes bugs that I didn't catch in the #5955. Among other things, commits must be signed, so we're utilizing the Team CLI Bot's keys to do the commit.

Where should the reviewer start?

Same as #5955

How should this be manually tested?

Same as #5955

What's the product update that needs to be communicated to CLI users?

None, infrastructure change.

[github-actions]

	Warnings
⚠️	There are multiple commits on your branch, please squash them locally before merging!
⚠️	"chore: signing commits, though unsure if it works for the github actions user" is too long. Keep the first line of your commit message under 72 characters.

Generated by 🚫 dangerJS against dc91cbc

[snyk-io]

🎉 Snyk checks have passed. No issues have been found so far.

✅ security/snyk check is complete. No issues have been found. (View Details)

✅ license/snyk check is complete. No issues have been found. (View Details)

✅ code/snyk check is complete. No issues have been found. (View Details)