[Improvements🛠️]:Update tools directory, CI workflow, and dependencies for better compatibility and performance

[wind111-lang]

Changed tools/semver-check.js

Node.js 10 was end-of-life on December 31, 2021.
so using process.versions.node to always use the current Node.js version.
This change solves fix GitHub Actions test failures caused by specifying Node.js '10.12.0'. node-sqlite3 testing with Node.js 18, so '10.12.0' isn’t need.

Changed tools/BinaryBuilder.Dockerfile

• Fixed network connectivity issue during tests on bullseye with Node.js 18.
  Added --maxsockets=1 to npm install as a temporary workaround.
  This fixes the error: Client network socket disconnected before secure TLS connection was established in bullseye CI test.
  • I would like to propose updating our test environment from bullseye to Bookworm. This change aims to leverage the latest software versions, security patches, and performance improvements offered by Bookworm.

Changed workflow CI

• Improved Apple Silicon compatibility by specifying arm64 architecture for macos-latest.
  • Is macos-m1 test working in self-host-runner? If this change has problem, I undo macos-latest in arm64.
• Updated setup-msbuild from v1 to v2 for better Windows11 compatibility.
• Removed setuptools installation step because node-gyp v10 supports Python 3.12 by default.
• Keep current version of upload-artifact due to test failures with the latest version.

Upgrade some dependencies

• Updated node-addon-api to 8.0.0 or higher. (Update dependency node-addon-api to v8 #1767 )
• Updated tar to 7.0.0 or higher. (Update dependency tar to v7 #1777 )
• Updated node-gyp to 10 or higher. (Update dependency node-gyp to v10 #1724 )

These updates improve compatibility, performance, and security of your project.

[YasharF]

Hey there, I am curious, what kind of tests have run to verify the version bump is not creating other issues, regressions, etc. ?

[wind111-lang]

Hello, @YasharF.
Thank you for your comment.

I have run the workflow in this PR and passed all environments with the changes in semver-check.js and BinaryBuilder.Dockerfile. Since I'm running the workflow on a fork repository, I'm not sure what the results will be on master repository Actions.

The issue was that the version checked in semver-check.js was specified as Node 10, causing the tests to fail. Additionally, on Debian bullseye, the tests passed after temporarily setting maxsockets=1 to fix the Client network socket disconnected before secure TLS connection was established error.

After making these changes, I ran the workflow with the updated versions from the Renovate PR, and all environments passed successfully.

Thank you.