Supress ProgressAction parameter from New-MarkdownHelp output

[chrisda]

Summary of the new feature / enhancement

Typically, I run New-MarkdownHelp (v14.2) in PowerShell 5.1x. I recently had occasion to run it in PowerShell 7.4.3. When I did, every cmdlet got a new ProgressAction parameter. According to about_CommonParameters, ProgressAction is a common parameter like Debug or Verbose. Unclear why only that common parameter is getting added to cmdlet articles.

Proposed technical implementation details (optional)

ProgressAction doesn't need to appear in the output of New-MarkdownHelp. This issue might be similar to the AsJob parameter as described in #339 (although AsJob was related to remote PowerShell).

[soulshined]

I tried forking and building from source but was having issues getting it done. Anyways, re:

Unclear why only that common parameter is getting added to cmdlet articles

See:

platyPS/src/platyPS/platyPS.psm1

Lines 2530 to 2547 in f9fa128

	function isCommonParameterName
	{
	param([string]$parameterName, [switch]$Workflow)
	if (@(
	'Verbose',
	'Debug',
	'ErrorAction',
	'WarningAction',
	'InformationAction',
	'ErrorVariable',
	'WarningVariable',
	'InformationVariable',
	'OutVariable',
	'OutBuffer',
	'PipelineVariable'
	) -contains $parameterName) {
	return $true

It's hard coded. Wouldn't something like this be future proof:

if ([System.Management.Automation.PSCmdlet]::CommonParameters.Contains($parameterName) -or
    [System.Management.Automation.PSCmdlet]::OptionalCommonParameters.Contains($parameterName)) {
       return true;
 }

[jdhitsolutions]

I believe this is being addressed in this PR I would love to get a new release with this fix.