PowerShell step generates a parse error when starting with [CmdletBinding()]

In my attempt to fix Jenkins-59529, I modified the powershellScript.ps1 file to wrap the user's script entered in the powershell/pwsh step in a try/catch. That unfortunately precludes the use of certain script elements e.g. [CmdletBinding()] and param() as they must appear at the top of the file before any other script or statements. There is a rather lengthy discussion of this on the GitHub PR that fixed Jenkins-59529 here.