Add operator or attribute to disable auto unrolling of pipe

Summary of the new feature / enhancement

As already discussed in other tickets the behavior of the pipe automatically unwrapping arrays of one is "by design" and not a bug, I'd like to request the addition of a new operator or attribute that changes this behavior in a non-breaking way instead of changing it for the pipe itself globally. Also it is very unintuitive that using the grouping operator has the opposite effect, instead of grouping everything together and signalling that it should be treated as a single input it'll cause the pipe to unroll the input.

Users may reasonably expect these two to be identical, but they're not:

$a = ConvertTo-Json -InputObject ('[[[0,1,2],[3,4,5]]]' | ConvertFrom-Json -NoEnumerate)
$b = ('[[[0,1,2],[3,4,5]]]' | ConvertFrom-Json -NoEnumerate) | ConvertTo-Json
$c = '[[[0,1,2],[3,4,5]]]' | ConvertFrom-Json -NoEnumerate | ConvertTo-Json
$a -eq $b
# False
$a -eq $c
# True

This isn't an issue as long as we use the output only ever as input to other PowerShell functions, but it becomes a big issue once we're interacting with other systems by e.g. writing a config file or preparing a REST-API call.

Proposed technical implementation details (optional)

Currently it is possible to somewhat work around this issue by using wrapping powershell classes, custom types, or explicite type definitions. However none of them is intuitive, self documenting or obvious to unsuspecting users.
Also it hinders using the pipe and makes code less powershelly by having to pass everything as an argument instead of using the pipe. And even then it may get lost within 3rd party module code and require if-else wrapping to fix the returned data structure afterward again.

1 Add an option to OutputTypeAttribute

e.g. by changing it's definition to:
[OutputType([<TypeLiteral>], ParameterSetName="<Name>", PipelineSupportAutoUnrolling=<Bool>)]

the name is WIP, as it would default to True this way which is not ideal, as most other attributes currently default to false and only when specified are true. This one however would have to be specified with =$false to get the new behavior.
An alternative name could be SuppressAutoUnrolling but that suggests that the auto unrolling is more of a bug than a feature...

2 Add a new Attribute

Similar to 1, but instead of adding it to the OutputType Attribute make it it's own. e.g. [SuppressAutoUnrolling()]

3 Add a new pipe operator

Instead of specifying the pipe behavior with the function definition (which at least allows to write wrapper functions or handle the enumeration internally) adding a new pipe operator in addition to |, && and ||, would allow developers to better account for the auto unrolling behavior right where it causes problems, when piping.
E.g. |> or ~| could be introduced to be almost like a normal pipe, but disable the unrolling of arrays with only one element and keep them as they are. This is probably the most flexible solution without breaking existing behavior and function.

It could be used like this:

$a = ConvertTo-Json -InputObject ('[[[0,1,2],[3,4,5]]]' | ConvertFrom-Json -NoEnumerate)
$b = ('[[[0,1,2],[3,4,5]]]' | ConvertFrom-Json -NoEnumerate) |> ConvertTo-Json
$c = '[[[0,1,2],[3,4,5]]]' | ConvertFrom-Json -NoEnumerate |> ConvertTo-Json
$a -eq $b
# True
$a -eq $c
# True

The issue names no files, tests, or implementation entry points. Start with the reproducible ConvertFrom-Json -NoEnumerate and ConvertTo-Json pipeline examples, then review the three proposed surfaces: OutputTypeAttribute, a new attribute, and a new pipe operator. Done means a non-breaking way to preserve single-element arrays through the pipe with equivalent JSON results.