Remove code specifically for PS 2.0-5.0

[xtqqczze]

          Should we let this stabilize for a patch or minor release before starting cleanup of PS 3/4 logic and syntax (like `New-Object` -> `::new()`) ?

Originally posted by @fflaten in #2432 (comment)

[fflaten]

Closing as no longer applicable. The PowerShell requirement change was delayed to next major release (v6).

[xtqqczze]

Since v6 development is ongoing on main, should this issue not remain open?

[fflaten]

We usually close issues on merge. Many parts of the backcompat code are already removed and released in 6.0.0-alpha1.

Please correct me if I misunderstood. 🙂

[xtqqczze]

e.g.

Pester/tst/functions/Output.Tests.ps1

Line 681 in 397724d

# Using internal code as [System.Management.Automation.Cmdlet]::CommonParameters is unavailable in PSv3

[fflaten]

Reopen to track future cleanup of PS v2/v3/v4/v5.0 code. Avoid large PRs and changes that doesn't provide a clear benefit.

E.g. changing this which would be unnecessary breaking change for projects migrating to Pester v6

Pester/src/functions/assertions/HaveParameter.ps1

Lines 277 to 291 in 337c213

	if ($Type) {
	# This block is not using `Format-Nicely`, as in PSv2 the output differs. Eg:
	# PS2> [System.DateTime]
	# PS5> [datetime]
	[type]$actualType = $ActualValue.Parameters[$ParameterName].ParameterType
	$testType = ($Type -eq $actualType)
	$filters += "$(if ($Negate) { 'not ' })of type [$($Type.FullName)]"
	if (-not $Negate -and -not $testType) {
	$buts += "it was of type [$($actualType.FullName)]"
	}
	elseif ($Negate -and $testType) {
	$buts += "it was of type [$($Type.FullName)]"
	}
	}