chore: CLI-1758 trigger Endpoint Explorer refresh after releases

[mattdolan-snyk]

What changed

• trigger the Endpoint Explorer snapshot refresh after successful Preview and Stable S3 publication
• run each trigger as a terminal CircleCI job with no downstream release dependencies
• dispatch the existing refresh-cli-data.yml workflow with the published channel
• cap the dispatch request at five seconds and convert missing credentials, transport failures, and non-204 responses into warnings
• add release-script tests for accepted dispatches and each non-blocking failure path

Why

The Endpoint Explorer should refresh when a public CLI channel changes, without waiting for the Explorer workflow or making CLI releases depend on Explorer availability.

The dispatch is best-effort. Once GitHub accepts the workflow request, the CLI pipeline does not follow or wait for the Explorer run. If the request cannot be made, the CLI release continues and the existing scheduled/manual Explorer refresh remains available as recovery.

Validation

• make format
• make lint
• go test ./... -skip TestBuildRecipeUsesGeneratedLSMetadataInLdflags in release-scripts
• bash -n release-scripts/trigger-endpoint-explorer-refresh.sh
• YAML parse of .circleci/config.yml
• verified the live snyk/endpoint-binary-explorer workflow still accepts workflow_dispatch with stable and preview channel inputs

The unmodified TestBuildRecipeUsesGeneratedLSMetadataInLdflags currently fails because its temporary CLI fixture does not include the help Markdown now required by the build recipe; the remaining release-script suite passes.

Deployment assumption

HAMMERHEAD_GITHUB_PAT must be able to dispatch Actions workflows in snyk/endpoint-binary-explorer. Missing or insufficient access is intentionally warning-only and does not fail the CLI release.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[snyk-io]

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

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues
✅	Licenses	0	0	0	0	0 issues
✅	Code Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[PeterSchafer]

Question: why didn't you just extend the existing mechanism we use for other examples?