error.stack: report frames at new X(...) at the new keyword - #37396

The slow-path column recount drops `provider->startPosition().m_column` (node:vm `columnOffset`) when `new` lands on the source's first physical line — e.g. `vm.runInContext('throw new\\nError("x")', ctx, {columnOffset:100})` reports `:1:7` where Node reports `:1:107`. The fast path preserves the offset by simple subtraction; the recount discards it. Fix: when the column loop exits at `i < 0` without finding a `'\n'`, add `provider->startPosition().m_column.zeroBasedInt()` to `column`.

The line-decrement and column-recount loops only test `source[i] == '\n'`, but JSC's lexer counts all four ECMAScript LineTerminators (LF, CR, U+2028, U+2029) when computing `expr.lineColumn`. When `new` and its callee are separated by a lone CR, LS, or PS in untranspiled (eval / `node:vm`) code, the slow path leaves the line at the divot's line and walks the column past the terminator — reporting a position on the wrong line. Extremely exotic trigger and cosmetic failure, but since this rewrite