Amend the Where-Object topic to explain the implicit Boolean logic that may be applied #3357

The v6 Where-Object topic now touches on implicit Boolean logic in the context of describing the new -Not parameter, but I don't think that's sufficient:

• The explanation of what property values will be considered $false is incomplete: the complete rules are in Introduce a new conceptual topic that explains to-Boolean coercion logic ("truthiness") #3356 - one option is to simply add a link to the proposed new topic.

• There is no mention of the positive variation: using just a -Property name and letting PowerShell's implicit to-Boolean coercion interpret the values, irrespective of their input type.

E.g., something like:

PS> 'hi', '', 'there' | Where-Object Length  # same as: Where-Object -Property Length
hi
there

is the concise equivalent of:

PS> 'hi', '', 'there' | Where-Object Length -gt 0
hi
there

By relying on 0 evaluating to $false and any nonzero value to $true in a Boolean context, the -gt 0 arguments aren't necessary.

Version(s) of document impacted

• Impacts 6.next document
• Impacts 6 document
• Impacts 5.1 document
• Impacts 5.0 document
• Impacts 4.0 document
• Impacts 3.0 document