Expand testcases with gradle project in root and gradle cli instead of gradlew

[mikepenz]

• add example of gradle project in root (without module)

[mikepenz]

Thank you for experimenting with this action @rwinch
I have seen that your sample usecase differs from the examples we currently had in our testcases. E.g. it being in the root, without module, also the output differs slightly.

This PR fixes the related issues, and also introduced a test-case covering this setup. In addition the repo now also includes a similar gradle project setup and runs the action on it.

• https://github.com/mikepenz/gradle-dependency-submission/pull/78/files#diff-faff1af3d8ff408964a57b2e475f69a6b7c7b71c9978cccc8f471798caac2c88R46-R53
• https://github.com/mikepenz/gradle-dependency-submission/pull/78/files#diff-cd9c591515f11a7f5187261bb80d5759d37588fee7c9e46cc82121a0c239ab25R18-R60

[mikepenz]

Hi @jhutchings1 , this change should also resolve the errors from: https://github.com/jhutchings1/elasticsearch/runs/7885067801?check_suite_focus=true

Please see the successful run here: https://github.com/mikepenz/elasticsearch/runs/7916531712?check_suite_focus=true
(in addition Java 17 was needed, and the write permission for the dependency submission API, also needed to enable the dependency graph for the fork)

And the import in the dependency submission UI: https://github.com/mikepenz/elasticsearch/network/dependencies

[jhutchings1]

Thanks for digging in on this @mikepenz ! I've been recommending lots of folks try this Action out, so appreciate all your continuing investment into it.

[mikepenz]

Thank you very much @jhutchings1 really appreciated.