Separate iCommands builder from "core" builder

[alanking]

Currently, an option called --icommands-only can be passed to the build script used by the builder container to only build iCommands in the core builder. I think we should just make these entirely separate builders.

The risk here is developers using the development environment will need to remember to re-build iCommands whenever irods-runtime changes to ensure that the right changes are being used in testing.

[korydraughn]

What's the motivation for separating them?

[alanking]

Simplifying things, mostly. Also gives us the option to move away from iCommands more easily in the future. Could also serve as an example "client builder", not that this would be highly valuable given the low number of C/C++ clients being developed. :)

[korydraughn]

I see. Got it, thanks.

[trel]

tiny boxes.