Adding support for -Verbose

[mwpreston]

Adding support for using the -Verbose switch when creating new reports with the New-AsBuiltReport cmdlet

Description

Added a simple if statement to check the presense of the -Verbose switch. If utilized, the PScribo cmdlets and Report related cmdlets are called with -Verbose, otherwise, they aren't.

Related Issue

Resolves Issue 28

Motivation and Context

This allows end users to specify whether or not they wish to see verbose logging messages on the console. This also allows developers of new reports to utilize the Write-Verbose cmdlet to better troubleshoot errors.

How Has This Been Tested?

Tested by running various reports specify verbose and not.

Screenshots (if appropriate):

Types of changes

• [ ] Bug fix (non-breaking change which fixes an issue)
• [ ] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• [x] My code follows the code style of this project.
• [x] My change requires a change to the documentation.
• [x] I have updated the documentation accordingly.
• [x] I have read the CONTRIBUTING document.

[mwpreston]

Hi - wondering if everything is all good here or if you need anything modified...? Looking to get some more testing done on the Rubrik piece, and this would certainly help me pin point errors when communicating back and forth with beta testers