Allow CI workflows on PRs to any branch

[FlorianPfaff]

Summary

• allow the test workflow to run for pull requests targeting any branch
• allow the MegaLinter workflow to run for pull requests targeting any branch
• keep existing push triggers limited to main

Testing

• Not run locally; workflow-only change verified by inspecting the branch diff.

[github-actions]

✅MegaLinter analysis: Success

Descriptor	Linter	Files	Fixed	Errors	Warnings	Elapsed time
✅ COPYPASTE	jscpd	yes		no	no	15.12s
✅ JSON	prettier	2	0	0	0	0.44s
✅ JSON	v8r	2		0	0	3.0s
✅ MARKDOWN	markdownlint	2	0	0	0	0.68s
✅ MARKDOWN	markdown-table-formatter	2	0	0	0	0.24s
✅ PYTHON	bandit	385		0	0	5.91s
✅ PYTHON	black	385	3	0	0	8.83s
✅ PYTHON	flake8	385		0	0	3.29s
✅ PYTHON	isort	385	4	0	0	0.75s
✅ PYTHON	mypy	385		0	0	5.24s
✅ PYTHON	pylint	385		0	0	119.19s
✅ PYTHON	ruff	385	4	0	0	0.07s
✅ REPOSITORY	checkov	yes		no	no	23.04s
✅ REPOSITORY	gitleaks	yes		no	no	7.6s
✅ REPOSITORY	git_diff	yes		no	no	0.03s
✅ REPOSITORY	secretlint	yes		no	no	7.19s
✅ REPOSITORY	syft	yes		no	no	5.54s
✅ REPOSITORY	trivy-sbom	yes		no	no	2.56s
✅ REPOSITORY	trufflehog	yes		no	no	19.91s
✅ YAML	prettier	4	0	0	0	0.49s
✅ YAML	v8r	4		0	0	4.9s
✅ YAML	yamllint	4		0	0	0.44s

See detailed reports in MegaLinter artifacts

Your project could benefit from a custom flavor, which would allow you to run only the linters you need, and thus improve runtime performances. (Skip this info by defining FLAVOR_SUGGESTIONS: false)

• Documentation: Custom Flavors
• Command: npx mega-linter-runner@9.4.0 --custom-flavor-setup --custom-flavor-linters PYTHON_PYLINT,PYTHON_BLACK,PYTHON_FLAKE8,PYTHON_ISORT,PYTHON_BANDIT,PYTHON_MYPY,PYTHON_RUFF,COPYPASTE_JSCPD,JSON_V8R,JSON_PRETTIER,MARKDOWN_MARKDOWNLINT,MARKDOWN_MARKDOWN_TABLE_FORMATTER,REPOSITORY_CHECKOV,REPOSITORY_GIT_DIFF,REPOSITORY_GITLEAKS,REPOSITORY_SECRETLINT,REPOSITORY_SYFT,REPOSITORY_TRIVY_SBOM,REPOSITORY_TRUFFLEHOG,YAML_PRETTIER,YAML_YAMLLINT,YAML_V8R

Show us your support by starring ⭐ the repository