1ES template integration follow-ups

[alzimmermsft]

Using the 1ES templates add required security checks, which is good, but this resulting in a few minutes to tens of minutes being added into pipeline runs. We should run a few "low hanging fruit" follow-up to optimize as best we can to reduce the overhead added.

• It appears the CredScan job runs with -b 3, indicating to use a batch size of three (relatively, parallelism). Can this be configured to the default value of the CredScan task which is 20 to speed up CredScan runs. And will changing this speed up CredScan?
• Can Component Governance be scoped down to the service being ran in CI. Component Governance doesn't work well with the structure of the Azure SDK pipelines as we're a mono repo that uses partitioned CI jobs but Component Governance attempts to build the root POM which fails in these partitioned CI jobs.
• Does the Microsoft Defender AntiMalware task configure CPU throttling appropriate to not throttle at all.
• Should we look into using ClamD instead of ClamAV for the AntiMalware step in *nix CI jobs. ClamD may have better performance and may be the long-term direction of the 1ES templates.

[github-actions[bot]]

@chenrujun @moarychan @netyyyy @saragluna

[github-actions[bot]]

Thank you for your feedback. Tagging and routing to the team member best able to assist.

[benbp]

FYI @scbedd

[scbedd]

Retagged @scbedd to get this back on my notifs