Add static analysis workflows

[esoergel]

This PR introduces a CodeQL workflow like we use in HQ to scan the Python and Ruby code in this repo.

It also adds Trivy, in two modes, "filesystem" mode, which scans packages and such (eg, checking for vulnerabilities in the ansible version), and config mode, which scans terraform files and others.

• OS packages and software dependencies in use (SBOM)
• Known vulnerabilities (CVEs)
• IaC issues and misconfigurations
• Sensitive information and secrets
• Software licenses

These will run only once a week or when specifically invoked. You can see the results from these scans here (filter by "Tool" to see which one reports what)

Environments Affected

None

[github-advanced-security]

This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation.