Updated gradle-dep-tree plugin and added support included builds

[michaelm-jf]

• 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.
• Updated the Contributing page / ReadMe page / CI Workflow files if needed.
• All changes are detailed at the description. if not already covered at JFrog Documentation, new documentation have been added.

---

Depends on:

• Use "included builds" when fetching related projects gradle-dep-tree#33

• Updated the gradle-dep-tree plugin, which has a new "use included builds" param
• Added support to configure the above param
• Updated the 'DepTreeNode' json structure to match the plugin output
• Added a UT that uses the new param, and a sample gradle project that uses composite builds

[attiasas]

Nice work, check out my comments

1. You should create the new flag in the flag maps and attach it to the related command (similar to other flags in the file)
2. I released the new version of the plugin with your changes. make sure you update and run the script that the v3.2.0 will be used and the embedded plugins test will pass
3. make sure all tests are passing

[attiasas]

make sure to define the flag and assign it to the related command (similar to other flags in the file)

[michaelm-jf]

Added it to the 'flagsMap'

[attiasas]

There are no issue using both flags, right?

[michaelm-jf]

You mean 'includeAllBuildFiles' and 'includeIncludedBuilds' ? They're not exactly related, 'includeAllBuildFiles' was already present before my change. It's used for for the gradle subprojects not for gradle included builds

[attiasas]

Is there a use for them here other than the logs? do we want to skip unresolved?
please make sure Xray can scan those dependencies by adding a test scan on a similar project and making sure Xray can handle those deps

[michaelm-jf]

'Configurations' is used to determine the dependency scope (direct, transitive, etc.). It contains values like 'compileOnly', 'testImplementaion', etc. which are in the Gradle spec.

'Unresolved' is not being used yet, I just added it to the struct in case we will want to take it into account.
I want to stress that those values are outputted by the gradle plugin but we just didn't unmarshall them into the struct