GeezerVison

Prior to this change, the documentation for `Group-Object`,
`Select-Object`, and `Sort-Object` did not specifically address using
those cmdlets against **hashtable** input.

In PowerShell 6 an improvement (see PowerShell/PowerShell#6934) enabled
users to reference the values of **hashtable** keys in these commands
without having to specify calculated properties.

This change:

- Updates the documentation for `Group-Object`, `Select-Object`, and
  `Sort-Object` in versions 7.0 and above to show how users can group,
  select, and sort **hashtable** objects by their key values
- Updates the documentation for `Group-Object`, `Select-Object`, and
  `Sort-Object` in Windows PowerShell 5.1 to show how users can group,
  select, and sort **hashtable** objects with calculated properties
- Cleans up Vale linting warnings across those files
- Fixes AB#20552
- Resolves MicrosoftDocs#9311

Prior to this change, the documentation for `Group-Object`,
`Select-Object`, and `Sort-Object` did not specifically address using
those cmdlets against **hashtable** input.

In PowerShell 6 an improvement (see PowerShell/PowerShell#6934) enabled
users to reference the values of **hashtable** keys in these commands
without having to specify calculated properties.

This change:

- Updates the documentation for `Group-Object`, `Select-Object`, and
  `Sort-Object` in versions 7.0 and above to show how users can group,
  select, and sort **hashtable** objects by their key values
- Updates the documentation for `Group-Object`, `Select-Object`, and
  `Sort-Object` in Windows PowerShell 5.1 to show how users can group,
  select, and sort **hashtable** objects with calculated properties
- Cleans up Vale linting warnings across those files
- Fixes AB#20552
- Resolves MicrosoftDocs#9311

Prior to this change, the documentation for `Group-Object`,
`Select-Object`, and `Sort-Object` did not specifically address using
those cmdlets against **hashtable** input.

In PowerShell 6 an improvement (see PowerShell/PowerShell#6934) enabled
users to reference the values of **hashtable** keys in these commands
without having to specify calculated properties.

This change:

- Updates the documentation for `Group-Object`, `Select-Object`, and
  `Sort-Object` in versions 7.0 and above to show how users can group,
  select, and sort **hashtable** objects by their key values
- Updates the documentation for `Group-Object`, `Select-Object`, and
  `Sort-Object` in Windows PowerShell 5.1 to show how users can group,
  select, and sort **hashtable** objects with calculated properties
- Cleans up Vale linting warnings across those files
- Fixes AB#20552
- Resolves #9311

…operties. (PowerShell#6934)

Measure-Object should handle `ScriptBlock` properties. Fixed by renaming `MshExpression` to `PSPropertyExpression` and making it public. Then in `MeasureObjectCommand`, lifting it up to the parameter level. Previously the implementation exposed the Property as a string and
wrapped it internally as a `PSPropertyExpression`. Now the parameter type is `PSPropertyExpression` directly allowing for both wildcard strings and `ScriptBlock`.

`PSPropertyExpression` now lives in a public namespace where it can be used by cmdlet and script authors to easily add the same type of functionality to their commands. I also modified `PSPropertyExpression` to handle hashtables properly as objects so
         @{prop = 3} | measure-object prop
and
         @{prop = 3} | measure-object {$_.prop}
will work the same. (Previously the example using just the property name would fail.)