[basitalisandhu]

Fixes #153 (reported to checkov as bridgecrewio/checkov#7713).

A unary operation followed by a newline and a binary operator fails to parse:

condition = alltrue([
  for n in var.names :
  length(n) > 0
  && !contains(["host"], n)
  && n != "x"
])

UnexpectedToken Token('__ANON_5', '&&') at line 9, column 7, though Terraform accepts it. checkov 3.3.19 to 3.3.22 pin bc-python-hcl2==0.4.3, so the whole file goes to parsing_errors and none of its resources are scanned.

In hcl2/hcl2.lark a bare expr_term can take trailing newlines (?expression : expr_term _NEW_LINE_OR_COMMENT* | ...) but unary_op can't, so after !contains(...) and a newline the parser can't reach binary_term. I added the same optional newline/comment slot after unary_op in ?operation. _NEW_LINE_OR_COMMENT is filtered and ?operation is inlined, so transformer output is unchanged.

New fixture unary_operator_newline.tf (+ JSON) covers !x then &&, !x then ||, -x then +, and a comment in between; it fails on master. pytest test/unit: 4 passed, 18 subtests (lark 1.3.1, Python 3.14), no LALR conflicts. I also parsed 1,862 .tf files (checkov's tests/terraform plus terraform-aws-modules eks, vpc, iam, rds) with both grammars: identical JSON for every file, and the same 7 fail both times, all intentionally invalid checkov fixtures like invalid_terraform_syntax/ and hcl_timeout/.