Integration test infrastructure set up

[joshpalis]

Description

This PR sets up the initial integration test cluster infrastructure. We iterate through all the zipArchive dependencies and install them into the cluster prior to installing the flow framework plugin. As we add support for additional plugin APIs, to add them to the test cluster, all we need to do is to add the related zipArchive under dependencies.

Additionally this PR fixes our ./gradlew run task which uses the integration test cluster. Now when you ./gradlew run both ML-commons and Flow Framework will be automatically installed into a local cluster

Issues Resolved

Part of #88

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

[amitgalitz]

Thanks for adding this! Could you change our DEVELOPER_GUIDE.md for the ./gradlew :run section to mention it also includes flow-framework and ml-commons installed

[amitgalitz]

LGTM! just one minor comment to update the developer guide

[joshpalis]

@owaiskazi19 I'm opting not to backport this to the feature/agent_framework branch since these dev branches are not published, therefore we cannot pull them in as zipArchive dependencies to install into our test clusters.

[ohltyler]

@owaiskazi19 I'm opting not to backport this to the feature/agent_framework branch since these dev branches are not published, therefore we cannot pull them in as zipArchive dependencies to install into our test clusters.

+1, there is no clean way to pull and build custom zips based on branches without extra boilerplate and workarounds that would need to be inevitably reverted.