CLI should use writeConveyorConfig VS printConveyorConfig

[manosbatsis]

Expect crazy errors when some random Gradle plugin or whatnot pollutes the output. In my case some android build version bumper was printing it's work, so i was getting:

manos@tower:~/git/foo$ conveyor make debian-package  --rerun 
❌ There was a problem parsing conveyor.conf.
Parse: Output of Gradle: 5: Key 'VersionCode 1206' may not be followed by token: 'gradle.build-dir' (if you intended 'gradle.build-dir' to be part of a key or string value, try enclosing the key or value in double
quotes)

Go figure eh? Took me a while to figure it out:

manos@tower:~/git/foo$ ./gradlew -q printConveyorConfig
VersionCode 1206
// Generated by the Conveyor Gradle plugin.

// Gradle project data. The build directory is useful for importing built files.
// ...

[mikehearn]

Yes, the current Gradle integration is kinda hacky. Using writeConveyorConfig will fix it but then there's a risk of the Gradle build and Conveyor getting out of sync. Conveyor could read the config to learn that Gradle is being used, then invoke Gradle to write out the config snippet, then reload the config. But I think a better way is probably to use the tooling API to read data out of the plugin via Gradle's own RPC system; their tooling API makes that fairly straightforward. It's probably also faster.