Do not make npm-groovy-lint crash when telemetry is failing

[github-actions[bot]]

🦙 MegaLinter status: ✅ SUCCESS

Descriptor	Linter	Files	Fixed	Errors	Elapsed time
✅ DOCKERFILE	hadolint	1		0	0.83s
✅ GROOVY	npm-groovy-lint	9	1	0	19.75s
✅ JAVASCRIPT	eslint	100	0	0	5.45s
✅ JAVASCRIPT	prettier	100	100	0	4.7s
✅ JSON	eslint-plugin-jsonc	9	0	0	2.15s
✅ JSON	jsonlint	9		0	0.19s
✅ JSON	npm-package-json-lint	yes		no	0.56s
✅ JSON	prettier	9	2	0	1.59s
✅ JSON	v8r	9		0	7.78s
✅ MARKDOWN	markdownlint	7	2	0	4.7s
✅ MARKDOWN	markdown-link-check	7		0	0.95s
✅ MARKDOWN	markdown-table-formatter	7	2	0	0.63s
✅ REPOSITORY	checkov	yes		no	13.86s
✅ REPOSITORY	gitleaks	yes		no	6.27s
✅ REPOSITORY	git_diff	yes		no	0.27s
✅ REPOSITORY	grype	yes		no	14.5s
✅ REPOSITORY	secretlint	yes		no	2.27s
✅ REPOSITORY	trivy	yes		no	7.75s
✅ REPOSITORY	trivy-sbom	yes		no	6.83s
✅ REPOSITORY	trufflehog	yes		no	5.87s
✅ SPELL	cspell	131		0	9.77s
✅ SPELL	lychee	19		0	3.75s
✅ XML	xmllint	1	0	0	0.12s
✅ YAML	prettier	3	0	0	0.5s
✅ YAML	v8r	3		0	10.37s
✅ YAML	yamllint	3		0	0.47s

See detailed report in MegaLinter reports

_MegaLinter is graciously provided by _

[stevenh]

Seems we both had a similar idea. In mine I put it in the analytics call so it would prevent errors in the case of not CLI, thoughts?