fix: harden compiler inputs and avoid root LSP scans

[yanghang8612]

Summary

• report a JSONError when settings.metadata.bytecodeHash has a non-string value
• remove shell command construction from regression helpers and keep split sources inside the output directory
• prevent the LSP project-directory strategy from recursively scanning the filesystem root when no workspace root is available

LSP scope

The LSP continues to allow absolute imports, include paths, and symlinks outside the workspace as upstream does. Only eager project discovery at a filesystem root is disabled; in that case the server analyzes directly opened and imported files instead.

Compatibility

This does not change contract ABI, bytecode, or runtime behavior. Normal workspace scanning and import resolution are unchanged. A client that deliberately uses the filesystem root as its project root no longer receives eager diagnostics for every Solidity file on the machine.

Tests

• rebuilt solc
• test/cmdlineTests.sh standard_wrong_type_bytecodeHash
• LSP regression: project-directory initialization without a workspace root
• existing LSP project-directory scanning test
• existing LSP relative-import test
• Python syntax checks and path/shell-metacharacter boundary checks for regressions.py and splitSources.py
• git diff --check

The repository-wide style check still reports the pre-existing trailing whitespace at .github/workflows/build.yml:322.

[github-actions]

Thank you for your contribution to the Solidity compiler! A team member will follow up shortly.

If you haven't read our contributing guidelines and our review checklist before, please do it now, this makes the reviewing process and accepting your contribution smoother.

If you have any questions or need our help, feel free to post them in the PR or talk to us directly on the #solidity-dev channel on Matrix.