`PSPossibleIncorrectUsageOfAssignmentOperator` fires when assigning value inside `if($())`

Before submitting a bug report:

• Make sure you are able to repro it on the latest released version
• Perform a quick search for existing issues to check if this bug has already been reported

Steps to reproduce

Invoke-ScriptAnalyzer -ScriptDefinition (
    [scriptblock]::Create{
        if (
            [bool]$(Try{$null=[datetime]('2024-11-12T09:44:00Z');$?}Catch{$false})
        ) {
            Write-Output -InputObject 'Could be parsed as datetime'
        }
        else {
            Write-Output -InputObject 'Could not be parsed as datetime'
        }
    }.ToString()
) -IncludeRule 'PSPossibleIncorrectUsageOfAssignmentOperator' | Format-List

Expected behavior

Actual behavior

RuleName : PSPossibleIncorrectUsageOfAssignmentOperator
Severity : Warning
Line     : 3
Column   : 30
Message  : Did you mean to use the assignment operator '='? The equality operator in PowerShell is 'eq'.

If an unexpected error was thrown then please report the full error details using e.g. $error[0] | Select-Object *

Environment data

PS > $PSVersionTable

Name                           Value
----                           -----
PSVersion                      7.4.6
PSEdition                      Core
GitCommitId                    7.4.6
OS                             Microsoft Windows 10.0.26100
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
WSManStackVersion              3.0

PS > (Get-Module -ListAvailable PSScriptAnalyzer).Version | ForEach-Object { $_.ToString() }

1.23.0

PS >

从提供的 Invoke-ScriptAnalyzer 复现和 PSPossibleIncorrectUsageOfAssignmentOperator 规则开始。跟踪嵌套的 if($()) 表达式是如何被分析的，然后检查现有规则覆盖中是否包含一个回归用例。当复现不再报告此误报，且现有分析器检查仍然通过时，即表示完成。