(#142) Skip PSSA analysis when there are no files (Script or Module) to analyze

[Windos]

Description Of Changes

This PR adds a check to determine if there are any Module or Script files to be analyzed before proceeding to attempt to pass a potentially NULL variable to PSScriptAnalyzer.

Motivation and Context

The Chocolatey GUI Licensed project includes script files but not modules files which was causing it's build to fail due to the resulting attempt to analyze a NULL path resulting in the error message is:

Cannot validate argument on parameter 'Path'. The argument is null. Provide a valid value for the argument, and then try running the command again.

Testing

This has been tested on a non-production build agent by manually editing the run-psscriptanalyzer.ps1 script and re-running the build.

Operating Systems Testing

Windows Server 2019

Change Types Made

• [X] Bug fix (non-breaking change).
• [ ] Feature / Enhancement (non-breaking change).
• [ ] Breaking change (fix or feature that could cause existing functionality to change).
• [ ] Documentation changes.
• [ ] PowerShell code changes.

Change Checklist

• [ ] Requires a change to the documentation.
• [ ] Documentation has been updated.
• [ ] Tests to cover my changes, have been added.
• [ ] All new and existing tests passed?
• [ ] PowerShell code changes: PowerShell v2 compatibility checked?

Related Issue

Fixes #142

[gep13]

@Windos thank you for getting this fixed up!