ci: replace TfSec by Trivy

[kayman-mk]

TfSec is outdated. The successor is Tricvy which is introduced by this PR.

[github-actions]

Hey @kayman-mk! 👋

Thank you for your contribution to the project. Please refer to the contribution rules for a quick overview of the process.

Make sure that this PR clearly explains:

• the problem being solved
• the best way a reviewer and you can test your changes

With submitting this PR you confirm that you hold the rights of the code added and agree that it will published under this LICENSE.

The following ChatOps commands are supported:

• /help: notifies a maintainer to help you out

Simply add a comment with the command in the first line. If you need to pass more information, separate it with a blank line from the command.

This message was generated automatically. You are welcome to improve it.

[github-actions]

✅MegaLinter analysis: Success

Descriptor	Linter	Files	Fixed	Errors	Warnings	Elapsed time
✅ ACTION	actionlint	2		0	0	0.28s
✅ COPYPASTE	jscpd	yes		no	no	1.79s
✅ REPOSITORY	checkov	yes		no	no	30.58s
✅ REPOSITORY	dustilock	yes		no	no	0.2s
✅ REPOSITORY	gitleaks	yes		no	no	0.93s
✅ REPOSITORY	git_diff	yes		no	no	0.01s
✅ REPOSITORY	grype	yes		no	no	38.83s
✅ REPOSITORY	kingfisher	yes		no	no	3.69s
✅ REPOSITORY	secretlint	yes		no	no	0.6s
✅ REPOSITORY	syft	yes		no	no	1.09s
✅ REPOSITORY	trivy-sbom	yes		no	no	0.13s
✅ REPOSITORY	trufflehog	yes		no	no	2.88s
✅ SPELL	cspell	3		0	0	3.03s
✅ YAML	prettier	2	0	0	0	0.56s
✅ YAML	v8r	2		0	0	2.41s
✅ YAML	yamllint	2		0	0	0.47s

See detailed reports in MegaLinter artifacts
Set VALIDATE_ALL_CODEBASE: true in mega-linter.yml to validate all sources, not only the diff

[github-advanced-security]

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

• The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
• Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
• You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.