Fix invalid workflow in CLI telemetry

[nicholaspcr]

Summary

Closes #7610

Changes

• Remove the panic from CLI telemetry workflow
• ...

Testing

Steps

...

Results

Regressions

...

Notes for Reviewers

When building the image locally I don't get the error but when using the latest stack image available I do get the telemetry panic. I want to update the docker-compose file to stop the failure in the CLI telemetry but I'm not sure what is causing the difference between the local docker image and the public available one.

Leaving this PR as a draft until I find out what is the cause of the discrepancy between local image and public available one.

Checklist

• Scope: The referenced issue is addressed, there are no unrelated changes.
• Compatibility: The changes are backwards compatible with existing API, storage, configuration and CLI, according to the compatibility commitments in README.md for the chosen target branch.
• Documentation: Relevant documentation is added or updated.
• Testing: The steps/process to test this feature are clearly explained including testing for regressions.
• Infrastructure: If infrastructural changes (e.g., new RPC, configuration) are needed, a separate issue is created in the infrastructural repositories.
• Changelog: Significant features, behavior changes, deprecations and fixes are added to CHANGELOG.md.
• Commits: Commit messages follow guidelines in CONTRIBUTING.md, there are no fixup commits left.