Improved tech detection when tech is provided by user

[eranturgeman]

• 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 ./....
• All static analysis checks passed.
• All tests have passed. If this feature is not already covered by the tests, new tests have been added.
• All changes are detailed at the description. if not already covered at JFrog Documentation, new documentation have been added.

---

This PR addresses an issue with incorrect technology detection in Yarn projects, particularly when there are multiple sub-projects that only contain a Yarn descriptor without any specific Yarn indicators. In a multi-project (but not multi-module) Yarn environment, if the inner projects only include the package.json file without any of Yarn’s standard indicators (.yarnrc.yml, yarn.lock, .yarn, “yarnrc”), the auto-detection mechanism incorrectly identifies these as NPM projects.

Since package.json cannot be used as an indicator for both NPM and Yarn to avoid conflicts, I implemented the following logic:
If the user specifies a particular technology (via command flags or the install command [Frogbot]), we take that into account when verifying the technology. This allows us to verify the specified technology using both its descriptors and indicators and not just its indicators.

As a result, when a ‘yarn install’ command is provided for a project and a package.json file is present, we can confidently determine that Yarn is being used, not NPM.

Another test case needs to be added to TestGetTechInformationFromWorkingDir. This test case discovered an issue that is fixed this PR: #179
The test case will be added along with the fix.

[attiasas]

Nice!, take a look at my comments.

[github-actions]

---

🐸 JFrog Frogbot