Resolve model editor queries from CodeQL packs if present

[koesie10]

This will start using the model editor endpoints queries from the CodeQL packs (codeql/java-queries and codeql/csharp-queries) if we can find the queries in those packs.

There are two cases (example language is Java):

• In case the queries are present in the codeql/java-queries, we don't need to write our own queries to disk. We still need to create a synthetic query pack so we can pass the queryDir to the query resolver without caring about whether the queries are present in the pack or not.
• In case the queries are not present in the codeql/java-queries, we need to write our own queries to disk. We will create a synthetic query pack and install its dependencies so it is fully independent and we can simply pass it through when resolving the queries.

These steps together ensure that later steps of the process don't need to keep track of whether the queries
are present in codeql/java-queries or in our own query pack. They just need to resolve the query.

Checklist

• CHANGELOG.md has been updated to incorporate all user visible changes made by this pull request.
• Issues have been created for any UI or other user-facing changes made by this pull request.
• [Maintainers only] If this pull request makes user-facing changes that require documentation changes, open a corresponding docs pull request in the github/codeql repo and add the ready-for-doc-review label there.

[starcke]

I think it looks ok, but a bit fiddy to have both paths active at the same time. Hopefully we can get rid of the writing after codeql have upgraded to the new packs.

[starcke]

I wonder if it would be neater to have two functions:

function tryResolveQueries(...) {
  const queries = await resolveQueriesFromPacks(...);
  return queries;
}

function resolveQueries(...)
  queries = tryResolveQueries(...)
  if (queries.length > 0) {
    return queries;
  }
   // No queries found. Determine the correct error message for the various scenarios.
  const humanConstraints = [];
...
}

and the caller could then call tryResolveQueries if the error handling is not needed.

Alternatively one could also call resolveQueriesFromPacks directly?

[koesie10]

👍, I think we can call resolveQueriesFromPacks directly, we don't need any of the additional functionality offered by resolveQueries.

[starcke]

This is basically unused right? it just needs to exist to satisfy the resolveEndpointsQuery inside runExternalApiQueries?

[koesie10]

Yes, exactly. This is just to reduce the amount of state that would need to be passed around between setUpPack and runExternalApiQueries.