Validate Yarn Version and Improve Error Messaging for Unsupported Versions

[fluxxBot]

• All tests have passed. If this feature is not already covered by the tests, new tests have been added.
• The pull request is targeting the dev branch.
• The code has been validated to compile successfully by running go vet ./....
• The code has been formatted properly using go fmt ./....

---

depends on:-

1. Verify supported Yarn version jfrog-cli-core#1347
2. Introduce Validation for Supported Yarn Versions jfrog-cli-artifactory#44

[EyalDelarea]

Please update the test cases to address new changes made to the other PRs.

Also i'm editing the PR title, as CLI pull requests will appear in the release notes of the CLI, and this is the place to notify users about the improvement that has been introduced here. ( also by the core and artifactory )

[fluxxBot]

this is required since yarn4 is not compatible with node16, this env will allow yarn4 tests to run in the same env.
Note: upgrading node16 to node18 causes legacyNpm tests to fail

[EyalDelarea]

Do we need all the yarn v4 tests now that we removed the support for yarnv4 commands?

[Ethorsen]

I'm not sure why you guys decide to drop support for the latest version of Yarn. But since we never experienced any problem with it we'll have to stick with jf 2.73.0 for now.