PR Summary

Fix #17110
When the PSCleanBlock experimental feature is not enabled, ProxyCommand.Create should not generate the clean block for the proxy function.

After the fix,

1. when the feature is disabled, generated proxy function for Get-Command doesn't have the clean block in it:

   PS:4> [System.Management.Automation.ProxyCommand]::Create($cm)
   [CmdletBinding(DefaultParameterSetName='CmdletSet', HelpUri='https://go.microsoft.com/fwlink/?LinkID=2096579')]
   param(
      .... ## skip the long param block
      )
   
   begin
   {
       ... ## skip the long begin block
   }
   
   process
   {
       try {
           $steppablePipeline.Process($_)
       } catch {
           throw
       }
   }
   
   end
   {
       try {
           $steppablePipeline.End()
       } catch {
           throw
       }
   }
   
   <#
   
   .ForwardHelpTargetName Microsoft.PowerShell.Core\Get-Command
   .ForwardHelpCategory Cmdlet
   
   #>

2. When the feature is enabled, the generated proxy function for Get-Command has the clean block in it:

   PS:3> [System.Management.Automation.ProxyCommand]::Create($cm)
   [CmdletBinding(DefaultParameterSetName='CmdletSet', HelpUri='https://go.microsoft.com/fwlink/?LinkID=2096579')]
   param(
      ... ## skip the long param block
       )
   
   begin
   {
       ... ## skip the long begin block
   }
   
   process
   {
       try {
           $steppablePipeline.Process($_)
       } catch {
           throw
       }
   }
   
   end
   {
       try {
           $steppablePipeline.End()
       } catch {
           throw
       }
   }
   
   clean
   {
       if ($null -ne $steppablePipeline) {
           $steppablePipeline.Clean()
       }
   }
   
   <#
   
   .ForwardHelpTargetName Microsoft.PowerShell.Core\Get-Command
   .ForwardHelpCategory Cmdlet
   
   #>

PR Checklist

• PR has a meaningful title
  • Use the present tense and imperative mood when describing your changes
• Summarized changes
• Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
• This PR is ready to merge and is not Work in Progress.
  • If the PR is work in progress, please add the prefix WIP: or [ WIP ] to the beginning of the title (the WIP bot will keep its status check at Pending while the prefix is present) and remove the prefix when the PR is ready.
• Breaking changes
  • None
  • OR
  • Experimental feature(s) needed
    • Experimental feature name(s):
• User-facing changes
  • Not Applicable
  • OR
  • Documentation needed
    • Issue filed:
• Testing - New and feature
  • N/A or can only be tested interactively
  • OR
  • Make sure you've added a new test if existing tests do not effectively test the code changed
• Tooling
  • I have considered the user experience from a tooling perspective and don't believe tooling will be impacted.