Add PSAvoidUsingNewObject Rule

[DrSkillIssue]

PR Summary

#2046

Adds a new built-in rule PSAvoidUsingNewObject that flags usage of the New-Object cmdlet and recommends using type literals with ::new() syntax instead for better performance and more idiomatic PowerShell code.

What Changed

• New Rule: AvoidUsingNewObject
• Severity: Warning
• Scope: Flags New-Object -TypeName usage while preserving New-Object -ComObject (COM objects cannot use type literals)

Key Features

• Smart COM Object Detection: Excludes New-Object -ComObject calls since they cannot be replaced with type literals
• Parameter Splatting Support: Handles complex scenarios where parameters are passed via hashtable splatting (New-Object @params)
• Variable Chain Resolution: Recursively follows variable assignments to determine if splatted parameters contain COM object references
• Comprehensive AST Analysis: Supports both direct parameter usage and various splatting patterns including $using: variables

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.

[DrSkillIssue]

@microsoft-github-policy-service agree