fix(cli.js): detect node-<version> binary, closes #6427

[amrbashir]

What kind of change does this PR introduce?

• Bugfix
• Feature
• Docs
• New Binding issue #___
• Code style update
• Refactor
• Build-related changes
• Other, please describe:

Does this PR introduce a breaking change?

• Yes, and the changes were approved in issue #___
• No

Checklist

• When resolving issues, they are referenced in the PR's title (e.g fix: remove a typo, closes #___, #___)
• A change file is added if any packages will require a version bump due to this PR per the instructions in the readme.
• I have added a convincing reason for adding this feature, if necessary

Other information

[TurtleIdiot]

I'm having the same issue and was about to make my own PR.

I've noticed an issue in the new regex proposed: /(nodejs|node)-*([1-9]*)*$/g

In regex, the hyphen is a special character and should ideally be escaped with a slash to prevent any errors. It is also important to consider the use of the asterisk character (marches 0 or more) over the question mark character (matches 0 or 1) since it would be unlikely for a node binary name to have more than one hyphen unless there is a good reson to.

I propose that the regex be changed to this instead:
/(nodejs|node)\-?([1-9]*)*$/g

[amrbashir]

In regex, the hyphen is a special character and should ideally be escaped with a slash to prevent any errors

hyphen is only special if it appears inside a range like [a-z], but won't hurt to escape it.

It is also important to consider the use of the asterisk character (marches 0 or more) over the question mark character (matches 0 or 1) since it would be unlikely for a node binary name to have more than one hyphen unless there is a good reson to.

Right, ? is better here, I will update it.