When executing the command with an empty string argument the generated PowerShell command incorrectly includes the value for the previous argument as value for the current one,

Expected Behavior:
When argument is an empty string (""), it should be omitted from the generated command
When argument is undefined, it should be omitted from the generated command
Only when argument has a meaningful value should it appear in the command

Actual Behavior:
Empty argument gets populated with the value of the previous argument.

Test Cases Demonstrating the Bug:

psCommandService.execute("setContent", {
        Path: "./test.txt",
        Value: "Test",
        Filter: ""
})

is expected to generate output:
Set-Content -Path './test.txt' -Value 'Test'

actual result:
Set-Content -Path './test.txt' -Value 'Test' -Filter 'Test'

Test has been updated to cover the fix for this scenario.