`qlt` subcommand should consistently support the same `--language` options

[data-douser]

Any qlt subcommand that defines a --language parameter should, ideally, support an equivalent list of --language options. If a subcommand does not currently define/specify the --language parameter as an option for that subcommand, then that subcommand is out-of-scope for the purposes of this issue.

Some work has already been proposed via PR #28 for the qlt query generate new-query subcommand.

Here is an example of the updated support, which looks good other than lacking the recently added/supported actions language:

$ qlt query generate new-query -h | grep 
'\-\-language'
  --language <c|cpp|csharp|go|java|javascript|python|ruby> (REQUIRED)  The language to generate a query for.

None of the qlt subcommands currently support actions as a language as CodeQL only added explicit language support for actions earlier this year.

The full list of --language values that should be supported by a given qlt subcommand is:

• actions
• c
• cpp
• csharp
• go
• java
• javascript
• python
• ruby

With a fresh build of the codeql-development-toolkit project/repo, it should be possible to use the --help for each subcommand while recursing through the diffirent subcommands of the qlt CLI (aka CodeQLToolkit.Core), looking just for the subcommands that support a --language parameter so that we can make the language options consistent across the codebase and CLI.

It should be useful to grep the codebase for instances of --language:

grep --color -rI '\-\-language' src/

When the changes are complete for this issue, the build should succeed and all tests -- including workflow checks via GitHub Actions -- associated with the codeql-development-toolkit project should continue to run without error.