Fix auto-detection of extractors that aren't languages

[henrymercer]

We tried to determine languages using codeql resolve languages, but that actually gives us extractors, and not all extractors are supported languages. We probably want to change our definition to something like "a -queries pack exists" when doing autodetection, but to get this fixed quickly, this PR reverts back to a hardcoded set.

Merge / deployment checklist

• Confirm this change is backwards compatible with existing workflows.
• Confirm the readme has been updated if necessary.
• Confirm the changelog has been updated if necessary.

[Copilot]

Pull Request Overview

This PR fixes an issue where the CodeQL Action was incorrectly auto-detecting extractors that aren't supported languages (like HTML, CSV, XML, etc.) when using codeql resolve languages. The fix reverts to using a hardcoded set of known languages as a temporary workaround.

• Adds a filter to only include extractors that are defined in the KnownLanguage enum
• Adds "actions" as a new known language and reorders the enum alphabetically
• Includes comprehensive test coverage for both specified and auto-detected unsupported extractors

Reviewed Changes

Copilot reviewed 8 out of 13 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
src/languages.ts	Adds "actions" language and reorders KnownLanguage enum alphabetically
src/config-utils.ts	Adds filtering logic to exclude extractors that aren't in KnownLanguage enum
src/config-utils.test.ts	Adds test cases for HTML extractor filtering in both specified and auto-detected scenarios
package.json	Version bump to 3.29.8
lib/ files	Compiled JavaScript output corresponding to TypeScript changes
CHANGELOG.md	Documents the bug fix for autodetection of unsupported languages