fix issue found for Set-AzVmssVMRunCommand

[grizzlytheodore]

Description

New parameter sets for Set-AzVMRunCommand and Set-AzVmssVMRunCommand were added in this PR(#19935) set to GA on 11/1,
but the feature owner @vivlingaiah has already found a bug(#19985), and I want to address them before it goes out.

Also adding examples here instead of in the PR that @vivlingaiah made in this PR: #19969

Checklist

• Check this box to confirm: I have read the Submitting Changes section of CONTRIBUTING.md and reviewed the following information:

• SHOULD select appropriate branch. Cmdlets from Autorest.PowerShell should go to generation branch.
• SHOULD make the title of PR clear and informative, and in the present imperative tense.
• SHOULD update ChangeLog.md file(s) appropriately
  • For any service, the ChangeLog.md file can be found at src/{{SERVICE}}/{{SERVICE}}/ChangeLog.md
  • A snippet outlining the change(s) made in the PR should be written under the ## Upcoming Release header in the past tense. Add changelog in description section if PR goes into generation branch.
  • Should not change ChangeLog.md if no new release is required, such as fixing test case only.
• SHOULD have approved design review for the changes in this repository (Microsoft internal only) with following situations
  • Create new module from scratch
  • Create new resource types which are not easy to conform to Azure PowerShell Design Guidelines
  • Create new resource type which name doesn't use module name as prefix
  • Have design question before implementation
• SHOULD regenerate markdown help files if there is cmdlet API change. Instruction
• SHOULD have proper test coverage for changes in pull request.
• SHOULD NOT introduce breaking changes in Az minor release except preview version.
• SHOULD NOT adjust version of module manually in pull request

[grizzlytheodore]

@dingmeng-xue , @VeryEarly pls see the description. The PR I made last week for this update has a bug and I want to address it before it goes out

[VeryEarly]

please create OOB request, it's too late for current release

[grizzlytheodore]

got it. spoke to the feature owner, and we will let this out in the next release scheduled on 12/6. Please review/merge

@VeryEarly

[Nickcandy]

It looks good to me. Please help me double check @BethanyZhou

[BethanyZhou]

Looks good to me with few changes required

[grizzlytheodore]

@BethanyZhou added back output blocks. Please review/merge !

[grizzlytheodore]

@Nickcandy looks all good. Please review/merge! thank you

[BethanyZhou]

Please add output for each example.

[grizzlytheodore]

Please add output for each example.

addressed your comment. pls review/merge

[BethanyZhou]

Looks good to me

[BethanyZhou]

Hi @Nickcandy , could you help carry @grizzlytheodore 's changes to main branch?

[Nickcandy]

@BethanyZhou Merged