Update codeql.yml with extended query pack

[brendankowitz]

Description

This pull request primarily focuses on refining the CodeQL scanning process in the .github/workflows/codeql.yml file. The changes include specifying the branches for the push trigger, ignoring certain file paths for pull requests, introducing a matrix strategy for languages, and updating the CodeQL initialization parameters.

Here are the key changes:

Changes to triggers:

• .github/workflows/codeql.yml: The push trigger now only applies to the main branch, and the pull_request trigger now ignores changes to .md, .json, and .http files.

Introduction of matrix strategy:

• .github/workflows/codeql.yml: A matrix strategy was introduced under jobs: to run CodeQL scans for both csharp and javascript languages.

Updates to CodeQL initialization:

• .github/workflows/codeql.yml: The CodeQL initialization parameters were updated to use the language from the matrix strategy and to include specific queries and query filters.

Testing

Builds successful

FHIR Team Checklist

• Update the title of the PR to be succinct and less than 65 characters
• Add a milestone to the PR for the sprint that it is merged (i.e. add S47)
• Tag the PR with the type of update: Bug, Build, Dependencies, Enhancement, New-Feature or Documentation
• Tag the PR with Open source, Azure API for FHIR (CosmosDB or common code) or Azure Healthcare APIs (SQL or common code) to specify where this change is intended to be released.
• Tag the PR with Schema Version backward compatible or Schema Version backward incompatible or Schema Version unchanged if this adds or updates Sql script which is/is not backward compatible with the code.
• CI is green before merge
• Review squash-merge requirements

Semver Change (docs)

Patch

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