Fix: Add license configuration to gitleaks workflow

[Adityav369]

Updates the gitleaks workflow to include required license configuration.

[jazzberry-ai]

Bug Report

| Name | Severity | Example test case | Description |
| GITLEAKS_LICENSE Exposure | High | Set GITLEAKS_LICENSE to a valid license, and then intentionally cause an error in the gitleaks configuration. | The GITLEAKS_LICENSE environment variable could be exposed in GitHub Actions logs due to misconfiguration or vulnerabilities in the gitleaks action. Although secrets are masked, there are ways to accidentally expose them. |
| Incorrect License Usage | Medium | Set GITLEAKS_LICENSE to an invalid license. | If the GITLEAKS_LICENSE is not correctly handled by the gitleaks action, the scan might not function correctly, leading to missed secrets. |
| Lack of Input Validation | Low | Set GITLEAKS_LICENSE to an invalid format. | The patch doesn't include any input validation for the GITLEAKS_LICENSE secret. This means that an invalid or malformed license could be passed to the action, potentially causing errors or unexpected behavior. |

_{Comments? Email us.}