feat(linter): added support to run in Node.JS legacy versions

[luizwbr]

With a few adjustments It is possible to run oxlint in projects which use legacy Node.js versions, such as 8.x.x. Basically this is possible by removing spread operator in 'binpath' environment assemble and changing a catch command to inform an error variable.

Without this modification, we got always this error:

node_modules/oxlint/bin/oxlint:23
  } catch {
          ^

SyntaxError: Unexpected token {
    at createScript (vm.js:74:10)
    at Object.runInThisContext (vm.js:116:10)
    at Module._compile (module.js:533:28)
    at Object.Module._extensions..js (module.js:580:10)
    at Module.load (module.js:503:32)
    at tryModuleLoad (module.js:466:12)
    at Function.Module._load (module.js:458:3)
    at Function.Module.runMain (module.js:605:10)
    at startup (bootstrap_node.js:158:16)
    at bootstrap_node.js:575:3

[graphite-app]

How to use the Graphite Merge Queue

Add either label to this PR to merge it via the merge queue:

• 0-merge - adds this PR to the back of the merge queue
• hotfix - for urgent hot fixes, skip the queue and merge this PR next

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

[Sysix]

Hello 👋
I do not know if the team wants to support this, but you have 2 problems with this current state:

• do not bump the version, the CI will auto bump it
• you forgot to update engines inside package.json

[luizwbr]

Hello 👋 I do not know if the team wants to support this, but you have 2 problems with this current state:

• do not bump the version, the CI will auto bump it
• you forgot to update engines inside package.json

All done!

[Boshen]

Thank you!