Add technology to audit params if provided by user through 'install' command

[x] All tests passed. If this feature is not already covered by the tests, I added new tests.
[x] This pull request is on the dev branch.
[x] I used gofmt for formatting the code before submitting the pull request.
[x] Update documentation about new features / new supported technologies

This PR updates the Audit parameters to include a specified technology from the install command, if provided.

This change leverages a new enhancement introduced here: https://github.com/jfrog/jfrog-cli-security/pull/175

In that improvement, we enhanced the technology detection when an install command is provided, allowing Frogbot to better handle complex structures where technologies are incorrectly identified. For instance, in a Yarn project with several sub-projects (not in a multi-module setup), where the sub-projects only have a package.json file without other Yarn indicators, these sub-projects are mistakenly identified as NPM projects.

This fix addresses that issue by enabling tech detection using descriptors when an install command is provided, rather than relying solely on indicators (which we typically use to avoid collisions between technologies with similar descriptors, like Yarn and NPM). If an install command is specified along with the working directories to scan (via frogbot-config.yml), we enforce this technology on each of the directories and use descriptors alone for verification, resolving the issue described.

jfrog / frogbot

Add technology to audit params if provided by user through 'install' command #749

[x] Update documentation about new features / new supported technologies