Export-CrescendoModule should directly accept command objects

[ethanbergstrom]

Since New-CrescendoCommand already exists, works well, and emits a Command object, it seems like an easy win from a scalable command generation and syntax checking/highlighting perspective for Export-CrescendoModule to directly accept an array of Command objects (ideally via the pipeline), just as it can accept an array of JSON configuration file paths.

For example:

New-CrescendoCommand -Verb 'Get' -Noun 'ChocoPackage' | %{
    $_.OriginalName = 'choco'
    $_.OriginalCommandElements = @(
        'search',
        '--limit-output',
        '--local-only'
    )
    $_.Description = 'Get installed Chocolatey packages'
    $_.Parameters = @(
        @{
            Name = 'Package'
            ParameterType = 'string'
            Description = 'Package Name'
        }
    )
    $_.OutputHandlers = @(
        @{
            ParameterSetName = 'Default'
            Handler = {
                param ( $output )
                $output | ForEach-Object {
                    $name,$version = $_ -split '\|'
                    [pscustomobject]@{
                        Name = $name
                        Version = $version
                    }
                }
            }
        }
    )
    $_
} | Export-CrescendoModule -ModuleName .\Get-ChocoPackage.psm1