Add engines in package.json to standardize node/npm versions

[sbolel]

Describe the problem and the solution you'd like

Is your feature request related to a problem? Please describe.

In order to standardize the node and npm versions, the engines property can be added to package.json.

Describe the solution you'd like

Sample engines property in package.json:

"engines": {
  "node": ">=18.0.0",
  "npm": ">=10.0.0"
},

Describe alternatives you've considered

n/a

Additional context

No response

Priority

None

[sawyerh]

I don't know if the template is the place for version manager tool-specific configs since this is oftentimes different across projects and individuals on the project — some use asdf, nvm, etc. I think adding minimum supported node version in package.json could make sense though.

Edit Updated the ticket description to reflect this

[sbolel]

That's a great point @sawyerh. Tools vary, but the engines field in package.json is consistent across the board. I updated the title of the issue to reflect that.