Format indention of multiline statements

Summary of the new feature

Enhance formatting of continued (multiline) statements (command and expression), combining the PipeLineIndentionStyle with statement continuation.

There are a lot of means to continue command statements, including pipe lines. especially so with expressions. I, myself, prefer all continued statements to be indented, but currently the formatting only supports indenting when a brace or parenthesis is involved, or optionally with a pipe line.

Proposed technical implementation details (optional)

I actually think the details of pipe line continuation gets simpler when the entire statement's continuation is taken in to account.

I am not fully understanding of how the formatting mechanism works, so this is a fundamental concept to how I would think it would work.

If using PowerShell AST's, for each PipeLineAst/CommandExpressionAst/etc, add 1 indention level to subsequent lines, in addition to all other indenting even for the same PipeLineAst.

There might be a need to restrict the continuation indention of a PipeLine or CommandExpression if they are the sole contents of a ParenExpression, because in that case, the PipeLine or CommandExpression is fully captured in the indention of the ParenExpression, as technically only one expression should appear in such cases, unlike a scriptblock or statementblock where multiple statements or expressions could appear.

I need to gather some examples to better demonstrate my use case.

Es werden keine Dateien oder Tests genannt. Beginne damit, den Formatierungsmechanismus und die PowerShell-AST-Behandlung für PipeLineAst und CommandExpressionAst zu lokalisieren; trage die fehlenden mehrzeiligen Beispiele zusammen und definiere anschließend die Vervollständigung als konsistente Fortsetzungseinrückung, einschließlich der genannten Unterscheidung bei Ausdrücken in Klammern, mit Tests, die das Verhalten abdecken.