Add CodeQL analysis workflow configuration

[xhuff]

Per NI Secure Development Lifecycle (SDL) guidance, enable Static Analysis Security Testing (SAST) via CodeQL

Analyzing source code and configuration prior to compilation provides a highly scalable method of security code review and helps ensure that secure policies are being followed. SAST is typically integrated into the commit pipeline to identify vulnerabilities each time the software is built or packaged. However, some offerings integrate into the developer environment to spot certain flaws such as the existence of unsafe or other banned functions and replace those with safer alternatives as the developer is actively coding. Development teams may decide the optimal frequency for performing SAST scans based on the product(s) they develop and may deploy multiple tactics—to balance productivity with adequate security coverage.

NOTE: this was an auto-generated change

[github-advanced-security]

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

• The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
• Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
• You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.