feat: add cve-query step

[jason1028kr]

What type of PR is this?
/kind feature

What this PR does / why we need it:
Pipeline changes for adding blocking criteria step

• SKIP_CVE_QUERY, QUERY_POOL env variables to specify runs/pools.
• trigger weekly release build from test build completion.
• running kusto query on a vm built on generic vhd image (could do this on 1es pool, but the code will eventually sit next to scanning when TME daily build is implemented. so decided on an implementation that mirrors scanning step).

Not sure it's worth it to change current weekly release build behavior to depend on test build, for this block functionality. Might be best to make this wait until daily build feature is done.

Which issue(s) this PR fixes:

Fixes #

Requirements:

• uses conventional commit messages
• includes documentation
• adds unit tests
• tested upgrade from previous version

Special notes for your reviewer:

Release note:

none

[cameronmeissner]

if this is coming from a variable group can you explicitly declare the group at the top of the yaml to minimize confusion?

[cameronmeissner]

Not sure it's worth it to change current weekly release build behavior to depend on test build, for this block functionality. Might be best to make this wait until daily build feature is done. I'd also prefer to hold off on this for now until we've ironed out any potential kinks.