Allow running packs with paths

[aeisenberg]

Also, use newer versions of the integration test packs that allow us to run with the latest CLI.

There are a few things of note here:

1. Previously, we had relied on the action to parse the pack name+version string and create a query suite for each string. This is no longer necessary (and not even possible if you add a path). Instead, we do some minimal checks to ensure the string is syntactically correct (further checks are done in the CLI itself). And instead we pass query specification strings around.
2. Because of the above, we no longer need to create a synthetic query string for each pack specification. We can just run each query specification directly.
3. We are running each specification in a separate command invocation because of command line length limitations in windows. I'm not really sure if this is a problem, but there was a comment in the code to that effect and I decided that we should run commands separately to be safe
4. This has an affect on how we check for ML query packs, mostly a simplification.
5. The qlpacks used for testing have their sources stored in our private repository and in order to update them, we need to edit them there. Perhaps we should move them to this repository.

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.

[cklin]

I think this also works (first character of string1 maps to first character of string2, and the second to the second, and so on):

tr "\r\n" "  "

[aeisenberg]

Oh...didn't know tr worked that way. Thanks.

[aeisenberg]

I'm about to make a minor change to this PR and I will ask for another review. Thanks for looking.

[aeisenberg]

Note that some required checks have been removed and that's why this is not mergeable. I am going to remove these as required checks and then recreate the list of required as described here: https://github.com/github/codeql-core/issues/1405#issuecomment-896190163

I'll make sure these instructions are easier to find.