Updated Gitleaks Action repository as the LICENSE has changed

[GoliathLabs]

With version v2.0.0 the license of the gitleaks-action has changed. A fork has been created which still uses the old license

Before enabling Gitleaks-Action Version 2, you will need to obtain a gitleaks-action license key from [gitleaks.io](https://gitleaks.io/products) if you are using gitleaks within the context of an organization. If you are using gitleaks-aciton on a user account's repo, you do not need a license key. You can sign up for a free license key that will grant you access to use gitleaks-action on one repo. The free tier sign up link will take you to a google forms page where you can fill out your information. After filling out your information, you should receive an email similar to the one below.

Source: https://github.com/gitleaks/gitleaks-action/releases/tag/v2.0.0

[mergeable]

Thanks for creating a pull request! A maintainer will review your changes shortly. Please don't be discouraged if it takes a while.

[DasSkelett]

So the new Gitleaks did find some "leaks".

• The first two aren't really leaks, the k8s quickstart.yml just included random placeholders that were generated during rendering of the Helm templates.
  04a37c7
• The third one was indeed a leak, some contributor pushed their local config.yaml in a PR before our fork. and removed it again in a follow-up commit (and unfortunately they were not squashed before merge, now we have this ugly add-then-remove in the history 🙄)
  • 3effed4
  • Path issues Place1/wg-access-server#7

Do you know how to tell Gitleaks that we don't care about these three?

[GoliathLabs]

@DasSkelett seems that there is a proper configuration for gitleaks where you can ignore certain commits https://github.com/zricethezav/gitleaks#configuration

I don't know if I can finish this today since I will be away from my computer later, but I will to get it done by tomorrow evening