Support json as an option for the remote target configuration in addition to csv

[SteveL-MSFT]

Remotely currently uses csv due to requirement to support PS2.0, however, we should consider supporting json as an option

[dcuomo]

+1 - In addition to SteveL's recommendation, could we also allow a parameterized list? For example: ... | Foreach-object { Remotely -SystemName $_ }

[dcuomo]

@SteveL-MSFT I modified remotely to accept a -SystemName parameter that I can iterate through. I pass through ConfigurationData.AllNodes.NodeName | Foreach-Object...which works well enough for my purposes. IMHO I think a better scenario would be for Pester to accept a -Remotely param in the context or describe blocks to run a group of tests against remote systems without adding a bunch of lines.

[SteveL-MSFT]

@dcuomo I believe we talked to the Pester team about supporting Remotely and they (at the time) thought it wasn't something they would support as part of the core which is why we have this as a separate repo. If you have something you think is useful to others, I encourage you to submit it as a PR :)