feat(build): delete test keys from repo

[paullatzelsperger]

WHAT

This PR adds scripts and tools to generate certificates and keys, so that we do not have them checked in the code base.

WHY

security guidelines prohibit checking in even test keys

FURTHER NOTES

• scripts should be used as much as possible to increase portability and user-friendlyness
• unless stated otherwise, a POSIX-compliant shell (e.g. bash) is assumed
• the following tools are presumed to be present:
  • openssl to generate certs/keys
  • yq to manipulate YAML files
  • base64 to encode/decode base64 strings

Closes #278

[gitguardian]

⚠️ GitGuardian has uncovered 1 secret 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 secret in your pull request

GitGuardian id	Secret	Commit	Filename
-	Generic Private Key	6ca8440	.github/workflows/deploy-test-secrets	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 secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
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>

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication

[paullatzelsperger]

I don't know why Gitguardian still complains, I did actually delete the hard-coded secret. Maybe it needs to run again after the merge