Need a way to test CG changes before checking them in

[lbussell]

Describe the Problem

Component governance is auto-injected into our 1ES Pipeline template jobs, including the "CG Code" pipeline. However, when the pipelines are run on non-production ("main" or "nightly" in our case) pipelines, the CG task doesn't run.

I would like a way to validate my CG fixes against the scanner before checking them in and getting surprised by what shows up. There may be an additional argument or parameter we can supply to the CG task or 1ESPT that forces CG to run (then we can feed it the "whatIf" parameter to make it a dry run).

[lbussell]

[Triage] A list of the CG task parameters is here: https://docs.opensource.microsoft.com/tools/cg/component-detection/variables/