Apply NewLineAfter option only for if-else clause

This constrains the behavior of PlaceCloseBrace rule when NewLineAfter option is set to true. Previously, if this option is set to true, the rule will trigger on any close brace that is not followed by a new line except if the close brace is part of a command element AND script block expression. This caused the rule to be too aggressive. We illustrate two such instances.

In the following instance the rule would add a new line between the close brace and the comma following it, which makes the command expression invalid.
```powershell
Some-Command -Param1 @{
 key="value"
},@{
 key="value"
}
```
would get formatted to
```powershell
Some-Command -Param1 @{
 key="value"
}
,@{
 key="value"
}
```

In the following instance the rule would add a new line between the close brace and the parameter following it, which again makes the command expression invalid.
```powershell
Some-Command -Param1 @{
 key="value"
} -Param2
```
would get formatted to
```powershell
Some-Command -Param1 @{
 key="value"
}
-Param2
```

Author: Kapil Borle

Rules/PlaceCloseBrace.cs

@@ -314,11 +314,9 @@ private DiagnosticRecord GetViolationForBraceShouldHaveNewLineAfter(
             if (tokens.Length > 1 && tokens.Length > expectedNewLinePos)
             {
                 var closeBraceToken = tokens[closeBracePos];
-                if (tokens[expectedNewLinePos].Kind != TokenKind.NewLine
-                    && tokens[expectedNewLinePos].Kind != TokenKind.Comment
-                    && !tokensToIgnore.Contains(tokens[closeBracePos]))
+                if ((tokens[expectedNewLinePos].Kind == TokenKind.Else
+                    || tokens[expectedNewLinePos].Kind == TokenKind.ElseIf))
                     {
-
                     return new DiagnosticRecord(
                         GetError(Strings.PlaceCloseBraceErrorShouldFollowNewLine),
                         closeBraceToken.Extent,