Invalid matching node and npm versions defaults to node 16

[otaviojacobi]

If you run a npm repo where node and npm versions do not match, such as:

...
 "engines": {
    "node": "^18.12.0",
    "npm": "^8.19.2"
  }
...

Rather than throwing an error, flowzone actually defaults to node 16 which makes understanding why your CI/CD broke harder.

[klutchell]

I think we could resolve this by making at least one engines check a requirement, with no fallback. We would have to update some repos that do not currently specify engine versions and have been getting by with the default v16.

Better yet, we could use the highest available node version matching the engine requirements and skip the rest. I don't recall why we didn't do that in the first place.