Adds Github Code Scanning (CodeQL)

[AlexandruAntonescuKeysight]

Summary

This PR adds a workflow which enables Github Code Scanning (the engine used is CodeQL).
It provides a suite of security queries that are run on every push and pull request on main branch. The results are visible in the security tab. This also represents a check in a PR context.
The scan is being done on python and C++ code (the C++ code needs a build step; I've built et_feeder as shared lib).

Example (the errors also appear as comments in the PR):

Test Plan

The testing was done by adding known bad lines of code to see if the problems are identified. An example could be seen in the picture above.

[github-actions]

MLCommons CLA bot All contributors have signed the MLCommons CLA ✍️ ✅

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

[TaekyungHeo]

Thanks, @AlexandruAntonescuKeysight. Do we need to update the paths as shown in "fixes include paths in the feeder after directory refactor"? Can you handle this in the YAML file instead? I would like to avoid changing the include path in the feeder. I assume someone uses it by adding the feeder directory as an include path. It also does not seem natural to have an include path starting with 'src,' at least for me.

[TaekyungHeo]

This will break downstream tools because the include path has been updated.

[danmih-ixia]

since the files have been moved from "et_feeder" to "src/feeder", the "et_feeder/et_feeder.h" paths are currently broken so need to be fixed. I think we should use #include "et_feeder.h" and add the include path as parameter at compile time.

[TaekyungHeo]

Yes, it makes sense. Please review and comment, @srinivas212

[srinivas212]

@AlexandruAntonescuKeysight @danmih-ixia @TaekyungHeo - are there any other opens? The paths issue has been fixed.

[danmih-ixia]

@AlexandruAntonescuKeysight @danmih-ixia @TaekyungHeo - are there any other opens? The paths issue has been fixed.

I don't think there is anything pending. The path issue has been submitted now, please check.