Fix compatibility rule tests by rjmholt · Pull Request #1697 · PowerShell/PSScriptAnalyzer

PR Summary

Fixes #1695.

We've been seeing failures in the compatibility rule tests, such as in #1696. This seems to be due to a hashtable key being null, which would be explained by a Pester 5 semantics issue. This attempts to simplify the situation to fix the issue.

PR Checklist

• PR has a meaningful title
  • Use the present tense and imperative mood when describing your changes
• Summarized changes
• Change is not breaking
• Make sure all .cs, .ps1 and .psm1 files have the correct copyright header
• Make sure you've added a new test if existing tests do not effectively test the code changed and/or updated documentation
• This PR is ready to merge and is not Work in Progress.
  • If the PR is work in progress, please add the prefix WIP: to the beginning of the title and remove the prefix when the PR is ready.

/cc @t-lipingma