feat(checkSyntax): create checkSyntaxStdin

[nurazon59]

resolve #295

[StantonMatt]

I checked this against #295 locally.

Validation passed:

• npm run compileOnce
• npx mocha -r ts-node/register test/test-python-shell.ts --grep "checkSyntaxStdin"
• npm test
• npx prettier --check index.ts test/test-python-shell.ts
• git diff --check origin/master...HEAD

No upstream checks are reported on this PR branch.

The behavior looks useful: the stdin path avoids creating pythonShellSyntaxCheck*.py temp files and the tests cover valid/invalid single-line and multiline syntax.

One thing I would tighten before merge: the test named should use pythonOptions from defaultOptions does not currently prove or implement that behavior. checkSyntaxStdin() builds the spawned argv as ["-c", "import sys; compile(...)"] and does not include defaultOptions.pythonOptions. I confirmed that with PythonShell.defaultOptions = { pythonOptions: ["--definitely-not-a-python-option"] }; checkSyntaxStdin("x=1") still passes because the option is ignored.

If option support is intended for this helper, it should include defaultOptions.pythonOptions in the spawned argv and test with a sentinel option that would fail if ignored. If not, I would rename or remove that test so the new API expectation stays clear.

[kikiminyes]

I found one mismatch between the added test and the implementation.

should use pythonOptions from defaultOptions sets PythonShell.defaultOptions = { pythonOptions: ['-B'] }, but checkSyntaxStdin() builds the subprocess args as only:

['-c', 'import sys; compile(sys.stdin.read(), "<stdin>", "exec")']

So the test currently only proves the method still succeeds while default options are set; it does not prove those options are passed to Python. I verified this with a mocked child_process.spawn: the recorded args are ['-c', ...], with no -B.

npm run compileOnce passes. I could not run the Python-backed tests in this local Windows environment because Python spawning is still failing here, so this check is limited to TypeScript compile plus the mocked spawn assertion.

I think either the implementation should include toArray(this.defaultOptions.pythonOptions) before -c, or the pythonOptions test should be removed/renamed if this API intentionally ignores default Python options.