docs: Update SLSA verification commands

[laurentsimon]

closes #14431

Checklist:

• Either (a) I've created an enhancement proposal and discussed it with the community, (b) this is a bug fix, or (c) this does not need to be in the release notes.
• The title of the PR states what changed and the related issues number (used for the release note).
• The title of the PR conforms to the Toolchain Guide
• I've included "Closes [ISSUE #]" or "Fixes [ISSUE #]" in the description to automatically close the associated issue.
• I've updated both the CLI and UI to expose my feature, or I plan to submit a second PR with them.
• [X ] Does this PR require documentation updates?
• I've updated documentation as required by this PR.
• Optional. My organization is added to USERS.md.
• I have signed off all my commits as required by DCO
• I have written unit and/or e2e tests for my change. PRs without these are unlikely to be merged.
• My build is green (troubleshooting builds).
• My new feature complies with the feature status guidelines.
• I have added a brief description of why this PR is necessary and/or what this PR solves.

Please see Contribution FAQs if you have questions about your pull-request.

[laurentsimon]

Let me know if there's something to do to fix pre-submits.

[34fathombelow]

@laurentsimon Thank you so much for the changes, they look great. LGTM! Just one request since this is a docs change. I appreciate the update in the GO dependencies, but could we do this in a separate PR? We will likely cherry-pick this back to our release-2.7 branch.

[laurentsimon]

@laurentsimon Thank you so much for the changes, they look great. LGTM! Just one request since this is a docs change. I appreciate the update in the GO dependencies, but could we do this in a separate PR? We will likely cherry-pick this back to our release-2.7 branch.

oops, totally. Was not supposed to be in the PR. I'll revert.

[laurentsimon]

@laurentsimon Thank you so much for the changes, they look great. LGTM! Just one request since this is a docs change. I appreciate the update in the GO dependencies, but could we do this in a separate PR? We will likely cherry-pick this back to our release-2.7 branch.

oops, totally. Was not supposed to be in the PR. I'll revert.

done.

[34fathombelow]

LGTM, Thanks again!

[codecov]

Codecov Report

Patch coverage has no change and project coverage change: -0.01 ⚠️

Comparison is base (7c5c72c) 49.73% compared to head (6c4ac18) 49.72%.

Additional details and impacted files

@@            Coverage Diff             @@
##           master   #14437      +/-   ##
==========================================
- Coverage   49.73%   49.72%   -0.01%     
==========================================
  Files         261      261              
  Lines       44705    44705              
==========================================
- Hits        22234    22230       -4     
- Misses      20284    20287       +3     
- Partials     2187     2188       +1     

see 2 files with indirect coverage changes

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

[crenshaw-dev]

/cherry-pick release-2.8

[crenshaw-dev]

/cherry-pick release-2.7