Forward all query metadata to the queryserver

[henrymercer]

This PR forwards all the query metadata to the queryserver.

Currently, only @kind and @id are forwarded for most users. This results in metadata errors when running some queries, even if the queries being run had the correct metadata. For example, the @kind metric query requires either the @tags summary metadata or the @metricType metadata key to be defined. However the VS Code extension doesn't currently forward the @tags and @metricType properties, so the queryserver reports errors whenever a user tries to run these queries.

With this PR, we forward all the query metadata to the queryserver, so queries like these will no longer report metadata errors.

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.
• @github/docs-content-codeql has been cc'd in all issues for UI or other user-facing changes made by this pull request.

[aeisenberg]

This looks fine. But just want to be sure that if a user accidentally includes invalid metadata, will the interpretation fail?

[henrymercer]

We currently generate metadata errors in (at least) two places: the metadata verifier, which is invoked during compilation, and the interpretation itself. For VS Code, only the metadata errors during the interpretation itself are problematic. I don't believe there are any cases where forwarding additional metadata would make the interpretation start failing.

[aeisenberg]

Thanks for the clarification. Yes, I think this needs a changelog entry.