wp-now: Restore node 18 support

[danielbachhuber]

Minimum supported version was bumped to node 20 in #82 (comment) but we should keep node 18 support for now.

Done is:

• Minimum supported version is 18.
• For any node 20 feature, we throw a warning (or error) if the current version is node 18.

[danielbachhuber]

@sejas Just wanted to let you know that @dmsnell worked through this and put together #90.

As it turns out, wp-now start still works fine on Node 18. wp-now start --blueprint=blueprint.json will crash, but that's documented now in the README. I think this is a fine place for now.

[sejas]

@danielbachhuber , @dmsnell, thank you for the change.

• I created this PR Change nvm node version to 18 #91 to be consistent with the rest of node version changes.

[dmsnell]

Thanks @sejas!

[amplify11dev]

@sejas Just wanted to let you know that @dmsnell worked through this and put together #90.

As it turns out, wp-now start still works fine on Node 18. wp-now start --blueprint=blueprint.json will crash, but that's documented now in the README. I think this is a fine place for now.

Where in the README does it call out it will crash in 18? I could be looking at the wrong repo/readme but I ran into this exact issue and didn't see it documented anywhere.

[danielbachhuber]

@amplify11dev It's mentioned in "Getting Started":

We could probably include a mention in the argument documentation too. Want to submit a PR for that?