Allow binary operators after nested object literals and bulleted arrays, fix ++ with bulleted arrays

[edemaine]

Fixes #1687. This bug was introduced by #1628 which innocently added checking for NestedImplicitObjectLiterals next to NestedBulletedArrays in MaybeNestedExpression.

It turns out the "right" answer is to check for neither! Otherwise, we don't allow for binary operators after dedent after the nested object literal / bulleted array. Conveniently, we already check for NestedImplicitObjectLiteral and NestedBulletedArray within PrimaryExpression (as part of ObjectLiteral and ArrayLiteral respectively), so we don't need to do anything special here, except for stopping the PushIndent Nested PopIndent check in MaybeNestedExpression.

Along the way, I fixed another issue with the concat operator ++ followed by a bulleted array. Previously, this broke for two reasons: (1) UpdateExpression thought that this was an increment, despite the indentation after ++ (needed to explicitly !Whitespace to match the comment). (2) WRHS did need to check explicitly for NestedImplicitObjectLiteral and NestedBulletedArray, like MaybeNestedExpression used to. (Here it's the right thing to do, because any further binary operators will be handled by the parent BinaryExpression.)

Also fixed some unrelated CI issues that seem to have come up just from 2025 deprecations.

[STRd6]

Thanks!