feature: Automated DAST scanning

[drcgjung]

WHAT

This PR introduces automated (and manual) DAST scanning using ZAP.

WHY

Manual DAST scanning is a tedious but critical effort. ZAP can be automated to perform these scans regularly and give more immediate feedback.

FURTHER NOTES

Please set the following (repository) secrets before activating/merging this PR (by personal communication with the requestor)

[gitguardian]

⚠️ GitGuardian has uncovered 4 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
-		Bearer Token	5739a30	.github/workflows/nuclei.yml	View secret
-		Bearer Token	356172c	.github/workflows/nuclei.yml	View secret
-		Bearer Token	5739a30	.github/workflows/nuclei.yml	View secret
-		Bearer Token	5678bc2	.github/workflows/nuclei.yml	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

<sup>🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

Our GitHub checks need improvements? Share your feedbacks!</sup>

[github-advanced-security]

KICS found more than 20 potential problems in the proposed changes. Check the Files changed tab for more details.

[drcgjung]

I'm fine with it. Commiter should remind the secret creation.

[drcgjung]

@RoKrish14 is that descheduling a common sense in tx?

[Martin0815bla]

• Copyright year not set to 2024 in kics.yml and README.md
• github code check failures in openapi.json (Array Without Maximum Number of Items (v3) Array schema has 'maxItems' set) 5 times

[drcgjung]

@RoKrish14 have to close this one as there were secrets in your git history