Observer configuration in fluo.properties needs way to handle commas in values

While trying to run the phrasecount application on an EC2 cluster with multiple zookeepers setup, my attempt to call `fluo init` failed because my fluo.properties file was invalid. This was due to an observer being configured with a zookeeper connection string that had commas in it (due to multiple servers). The commas caused an error to be thrown and stopped initialization.

This script creates the `fluo.properties` file:

https://github.com/fluo-io/phrasecount/blob/master/bin/configure.sh#L39

Start with phrasecount/bin/configure.sh at line 39 and reproduce the failure using a zookeeper connection string containing commas in fluo.properties. Trace how fluo init parses observer configuration and identify the relevant tests or initialization path. Done means a comma-containing observer value is accepted and initialization no longer rejects the properties file.

Written by the indexing model from the issue text.