Enable CodeQL as SAST Tool

[joycebrum]

Closes #1300

I've configured it to run on c files and python.

For C, I've configured manually the build using as example the build.yml workflow. Let me know if I missed anything. There were only 10 findings on the codeql run.

As you said, I focused on the C build and just kept the python part because the autobuild was working well for it. Let me know if it would be better to drop it.

[ci-tester-lunarg]

Author joycebrum not on autobuild list. Waiting for curator authorization before starting CI build.

[ci-tester-lunarg]

Author joycebrum not on autobuild list. Waiting for curator authorization before starting CI build.

[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.

[charles-lunarg]

The only change I'd like to ask is to squash the commits down into one. Otherwise it looks very nice. I see the list of issues the code analyzer found, and will create PR for them shortly.

[ci-tester-lunarg]

Author joycebrum not on autobuild list. Waiting for curator authorization before starting CI build.

[ci-tester-lunarg]

Author joycebrum not on autobuild list. Waiting for curator authorization before starting CI build.

[charles-lunarg]

Just wanted to say thanks for doing the legwork of implementing this! Very nice to have and already has found some questionable code!