fix: bring back expression eol operator continuation

Author: DylanPiercey

src/__tests__/fixtures/attr-operators-newline-after.skip/__snapshots__/attr-operators-newline-after.expected.txt renamed to src/__tests__/fixtures/attr-operators-newline-after/__snapshots__/attr-operators-newline-after.expected.txt

@@ -136,13 +136,8 @@ export const EXPRESSION: StateDefinition<ExpressionMeta> = {
       !expression.groupStack.length &&
       (expression.terminatedByWhitespace || expression.terminatedByEOL)
     ) {
-      this.exitState();
-
-      // TODO: eventually it'd be good to allow multi line expressions.
-      // This currently has a number of edge cases and likely can only be solved by
-      // converting the expression state to avoid the look ahead/behind regexp pattern and instead
-      // check characters as is goes.
-      // if (checkForOperators(this, expression)) this.forward = 1;
+      if (checkForOperators(this, expression)) this.forward = 1;
+      else this.exitState();
     }
   },
 
@@ -238,9 +233,10 @@ function checkForOperators(parser: Parser, expression: ExpressionMeta) {
     return false;
   }
 
-  const pattern = parser.isConcise
-    ? conciseOperatorPattern
-    : htmlOperatorPattern;
+  const pattern =
+    parser.isConcise || expression.terminatedByEOL
+      ? conciseOperatorPattern
+      : htmlOperatorPattern;
   pattern.lastIndex = parser.pos;
   const matches = pattern.exec(parser.data);