Support install-tool without associated version or env variable

[rarkins]

I would like for install-tool node to work even if there's no NODE_VERSION defined. In such cases Containerbase should resolve the latest stable version and install that. This should work for all install-tool commands.

---

• java 9fabcd0
  • gradle 9fabcd0
  • maven feat(java): add maven version resolver #2871
• node feat(cli/node): install latest node and npm tool versions #1828
  • npm, pnpm, yarn ...
• php
  • composer feat(php): convert composer installer #2848
• python
  • install-pip feat(cli/python): convert tools and add install-pip command #3015
  • checkov feat(cli/python): convert tools and add install-pip command #3015
  • copier feat(cli/python): convert tools and add install-pip command #3015
  • hashin feat(cli/python): convert tools and add install-pip command #3015
  • pdm feat(cli/python): convert tools and add install-pip command #3015
  • pip-tools feat(cli/python): convert tools and add install-pip command #3015
  • pipenv feat(cli/python): convert tools and add install-pip command #3015
  • poetry feat(cli/python): convert tools and add install-pip command #3015

[viceice]

Should we install lts if available or latest version (eg node v20 vs v21)?

[rarkins]

Latest stable for each associated tool. Today in node versioning we consider non-LTS to be unstable (which is not quite correct.. but it's what we got). So in short, that's Node 20.