feat: disable container app scan with feature flag #4105

[tommyknows]

• Follows CONTRIBUTING rules

What does this PR do?

This commit adds a check for the containerCliAppVulnsEnabled feature flag. If neither --exclude-app-vulns nor --app-vulns are set, the feature flag will be used to determine whether app vulnerabilities will be scanned or not.

This commit was merged in #4105 and reverted in #4184 again due to an issue with the global-agent patch.
This PR now builds on top of #4205 instead.

[github-actions]

	Warnings
⚠️	Since the CLI is unifying on a standard and improved tooling, we're starting to migrate old-style imports and exports to ES6 ones. A file you've modified is using either module.exports or require(). If you can, please update them to ES6 import syntax and export syntax. Files found: src/cli/commands/monitor/index.ts src/cli/commands/test/index.ts test/tap/cli-monitor.acceptance.test.ts

Generated by 🚫 dangerJS against b12216d

[stepsize]

New TODO comment introduced here:

      // TODO: we should be able to remove that setting once once we remove the
      // containerCliAppVulnsEnabled feature flag has been removed as well.
      // Currently without setting this (or app-vulns), the code tries to reach
      // the API to check the feature flag and throws an exception.

Consider fixing it now or converting it into an issue to raise visibility.

_{Mention [stepsize] in a comment to create an issue out of this TODO. See examples here.}

[stepsize]

New TODO comment introduced here:

      // TODO: we should be able to remove that setting once once we remove the
      // containerCliAppVulnsEnabled feature flag has been removed as well.
      // Currently without setting this (or app-vulns), the code tries to reach
      // the API to check the feature flag and throws an exception.

Consider fixing it now or converting it into an issue to raise visibility.

_{Mention [stepsize] in a comment to create an issue out of this TODO. See examples here.}

[michelkaporin]

Great 👍