fix(dev-env): avoid false use matches in SQL imports

[sjinks]

Description

Fixes a false positive in dev-env SQL validation where UTF-8 bytes for U+2028 inside SQL data could be decoded as line separators. When the following string content started with Use , the existing USE statement check saw a synthetic line and rejected the import.

The validator now reads SQL input with binary line decoding and waits for the reader close event before post-validation summaries. Related: PLTFRM-2430.

Changelog Description

Fixed

• Dev-env: Fixed false positive SQL import validation errors for exported dumps containing Unicode line-separator bytes inside string data.

Pull request checklist

• Update SETUP.md with any new environmental variables.
• Update the documentation.
• Manually test the relevant changes.
• Follow the pull request checklist
• Add/update automated tests as needed.

New release checklist

• Automated tests pass.
• The Preparing for release checklist is completed.

Steps to Test

1. Check out this PR.
2. Run npm run jest -- --runTestsByPath __tests__/lib/validations/sql.js.
3. Confirm the SQL validation suite passes, including the regression coverage for raw E2 80 A8 bytes followed by Use Cases inside an INSERT value.

[github-actions]

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Scanned Files

None

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[Copilot]

Pull request overview

Fixes a false‑positive in dev‑env SQL import validation where UTF‑8 bytes for U+2028 (E2 80 A8) inside string data were decoded by Node's readline as line separators, causing the next characters (e.g. Use Cases…) to be treated as a new line that triggered the ^USE check. The fix switches the shared line reader to FileHandle.readLines({ encoding: 'binary' }), so only \n/\r\n split lines and the embedded U+2028 bytes remain inside the value. It also simplifies the close‑awaiting with once(readInterface, 'close').

Changes:

• Replace createReadStream + readline.createInterface with FileHandle.readLines({ encoding: 'binary' }) in getReadInterface.
• Use await once(readInterface, 'close') in both fileLineValidations and validate instead of the manual promise+close pattern.
• Add a regression test that writes raw E2 80 A8 bytes inside an INSERT value followed by Use Cases and asserts no USE <DATABASE_NAME> error.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.

File	Description
src/lib/validations/line-by-line.ts	Switches reader to binary readLines() so U+2028/U+2029 bytes are not treated as line breaks; uses once() for close.
src/lib/validations/sql.ts	Uses once(readInterface, 'close') to await stream completion.
tests/lib/validations/sql.js	Adds regression test verifying dev‑env validation does not flag text following raw U+2028 bytes as a USE statement.