Fix: adding dast fortidevsec workflow

[robinmordasiewicz]

Fixes an issue with our FortiDevSec workflow. Previously, the workflow was checking for the existence of secrets FORTIDASTORGID and FORTIDASTAPPID, but it should actually be checking for FORTIDEVSECORGID and FORTIDEVSECAPPID. This fix ensures that the workflow correctly detects the presence of the required secrets.

By making this change, we ensure that the FortiDevSec workflow runs smoothly and accurately. This improves the overall security of our project by properly integrating the FortiDevSec tooling into our CI/CD pipeline.

[github-actions]

🦙 MegaLinter status: ✅ SUCCESS

Descriptor	Linter	Files	Fixed	Errors	Elapsed time
✅ ACTION	actionlint	1		0	0.03s
✅ COPYPASTE	jscpd	yes		no	1.46s
✅ REPOSITORY	checkov	yes		no	16.41s
✅ REPOSITORY	dustilock	yes		no	0.48s
✅ REPOSITORY	gitleaks	yes		no	19.5s
✅ REPOSITORY	git_diff	yes		no	0.07s
✅ REPOSITORY	grype	yes		no	16.14s
✅ REPOSITORY	kics	yes		no	66.77s
✅ REPOSITORY	secretlint	yes		no	1.43s
✅ REPOSITORY	syft	yes		no	0.41s
✅ REPOSITORY	trivy	yes		no	7.99s
✅ REPOSITORY	trivy-sbom	yes		no	3.21s
✅ REPOSITORY	trufflehog	yes		no	13.52s
✅ YAML	prettier	1	0	0	0.69s
✅ YAML	v8r	1		0	2.77s
✅ YAML	yamllint	1		0	0.49s

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

MegaLinter is graciously provided by