Add test ns query under var-query field

[deadeyejoe]

Closes #1981.

What has changed?

Running a single test would result in every test in every namespace being run. This was because the test var query was being spread into the nrepl payload, rather than being passed as 'var-query'.

Looks to have been introduced by commit f7844f3.

My Calva PR Checklist

If this PR involves only documentation changes, I have:

• [ ~] Read Editing Documentation
• [ ~] Directed this pull request at the published branch.
• [ ~] Built the site locally (if the changes were more involved than simple typo fixes), and verified that the site is presented as expected.
• [ ~] Referenced the issue I am fixing/addressing in a commit message for the pull request (if there was is an issue for the documentation change)
  • [~] If I am fixing the issue, I have used GitHub's fixes/closes syntax
  • [~] If I am fixing just part of the issue, I have just referenced it w/o any of the "fixes” keywords.

If this PR involves code changes, I have:

• Read How to Contribute.
• Directed this pull request at the dev branch. (Or have specific reasons to target some other branch.)
• Made sure I have changed the PR base branch, so that it is not published. (Sorry for the nagging.)
• Updated the [Unreleased] entry in CHANGELOG.md, linking the issue(s) that the PR is addressing.
• Figured if anything about the fix warrants tests on Mac/Linux/Windows/Remote/Whatever, and either tested it there if so, or mentioned it in the PR.
• [~] Added to or updated docs in this branch, if appropriate
• [~] Tests
  • Tested the particular change
  • Figured if the change might have some side effects and tested those as well.
  • Smoke tested the extension as such.
  • Tested the VSIX built from the PR (so, after you've submitted the PR). You'll find the artifacts by clicking Show all checks in the CI section of the PR page, and then Details on the ci/circleci: build test.
• Referenced the issue I am fixing/addressing in a commit message for the pull request.
  • If I am fixing the issue, I have used GitHub's fixes/closes syntax
  • [~] If I am fixing just part of the issue, I have just referenced it w/o any of the "fixes” keywords.
• [~] Created the issue I am fixing/addressing, if it was not present.
• Formatted all JavaScript and TypeScript code that was changed. (use the prettier extension or run npm run prettier-format)
• Confirmed that there are no linter warnings or errors (use the eslint extension, run npm run eslint before creating your PR, or run npm run eslint-watch to eslint as you go).

Ping @PEZ, @bpringe, @corasaurus-hex, @Cyrik

[PEZ]

Thanks for contributing! 🙏 ❤️

By the wording in the PR, it seems like you have found the right place to fix it. Haven't had a look yet. Will tomorrow! Prepping for this event right now: https://www.meetup.com/london-clojurians/events/286030325/ 😄

[bpringe]

@PEZ I'm not sure why that build-test workflow fails while packaging the vsix.

[webpack-cli] Error: error:0308010C:digital envelope routines::unsupported

[PEZ]

@PEZ I'm not sure why that build-test workflow fails while packaging the vsix.

[webpack-cli] Error: error:0308010C:digital envelope routines::unsupported

That is a very, very strange, and worrying, error. I'll have a look later today.

[PEZ]

I find this issue, which seems to have cause a ruckus in the Webpack community:

• nodejs 17: digital envelope routines::unsupported webpack/webpack#14532

It is many, many pages of comments. Seems like the conclusion is to upgrade to Webpack 5. Which sucks a bit for us, because that is what we are using! But anyway, now I am not as scared by this error. I'm sure we'll at least find a workaround with some sensible amount of work.

[PEZ]

I've reproduced the error in a separate branch. Let's see if I can figure out a way to fix it.

[PEZ]

OK, sorry that your PR got a bit messy with the Webpack business, @deadeyejoe. But now we have a workaround/maybe-fix on dev, so please merge that and I think (hope) this build will turn green.

[deadeyejoe]

Fingers crossed!

[bpringe]

Thanks again, @deadeyejoe!