(#85) Add globbing pattern for integration tests

[gep13]

Description Of Changes

This commit switches to having two globbing patterns, one for unit tests and another for integration tests, and based on the test execution type that is running, these globbing patterns will either be used individually, or combined.

Motivation and Context

Previously, there was an assumption that a single globbing pattern that could be provided that would allow the selection of the files that needed to be tested, for both unit and integration tests. However, in practice, this turned out to not be teh case, as it was over-somplicated, and prone to error.

Testing

Using the choco-licensed code base as a test bed, the following was done:

1. .\build.bat --target=Test-NUnit --exclusive --testExecutionType=unit
2. .\build.bat --target=Test-NUnit --exclusive --testExecutionType=integration
3. .\build.bat --target=Test-NUnit --exclusive --testExecutionType=all

In each case, make sure that everything is run to completion and is successful, and then verify that the correct test assemblies are located and tested.

Change Types Made

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

Related Issue

Fixes #85

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 v2 compatibility checked.

[AdmiringWorm]

@gep13 thanks for getting this added