feat: add --expect-results and --exepect-result-count to npm query

[wraithgar]

This will allow users to tell npm whether or not to exit with an exit
code depending on if the command had any resulting entries or not.

[npm-cli-bot]

found 1 benchmarks with statistically significant performance improvements

• app-medium: no-cache

found 1 benchmarks with statistically significant performance regressions

• app-medium: cache-only

timing results

app-large	clean	lock-only	cache-only	cache-only peer-deps	modules-only	no-lock	no-cache	no-modules	no-clean	no-clean audit
npm@8	48.922 ±9.37	19.985 ±0.02	18.397 ±0.17	23.266 ±3.11	3.570 ±0.23	3.453 ±0.09	2.870 ±0.10	12.881 ±0.16	2.678 ±0.09	4.762 ±1.01
#5966	45.712 ±0.75	19.826 ±0.10	18.267 ±0.05	21.372 ±0.83	3.363 ±0.01	3.398 ±0.06	2.623 ±0.02	12.794 ±0.00	2.637 ±0.01	3.979 ±0.15

app-medium	clean	lock-only	cache-only	cache-only peer-deps	modules-only	no-lock	no-cache	no-modules	no-clean	no-clean audit
npm@8	30.397 ±1.58	15.453 ±0.12	12.839 ±0.03	15.202 ±0.16	3.121 ±0.02	3.230 ±0.04	3.151 ±0.18	10.143 ±0.10	2.642 ±0.07	3.603 ±0.04
#5966	29.553 ±1.50	15.301 ±0.09	14.277 ±0.18	15.234 ±0.14	3.067 ±0.06	3.125 ±0.07	2.746 ±0.09	9.899 ±0.07	2.512 ±0.03	3.620 ±0.09

[ruyadorno]

LGTM 👍

[lukekarrys]

Rebased onto latest to fix conflicts

[lukekarrys]

i pushed a commit converting to the new test config format which uncovered an interesting bug. the config type definition is converting all numbers to booleans (https://github.com/npm/cli/actions/runs/3820159448/jobs/6498253762#step:7:70).

with nopt there doesn’t seem to be a way to make a config that can be both a number and boolean that i could find?

[wraithgar]

Well fiddlesticks, that's frustrating. We'll have to either get creative or ditch the numbers for now.

[wraithgar]

So far from what I've seen discussed, the big asks have been for boolean, and for "more than one entry" (think react hoisting).

[lukekarrys]

Approved with one question that is not a blocker.