Configuration for nodes (zookeeper & config files) is confusion and inconsistent between node types

Configuing nodes is faily confusing! For example, brokers and servers require `-zkAddress` parameters, whether or not they are provided a `-configFileName`. Meanwhile, controllers do not allow that parameter if a `-configFileName` is provided and instead has `controller.zk.str` configuration value. Same for the the `-clusterName` and `controller.helix.cluster.name` configuration value.

This difference makes orchestration confusing.

Also, as a user the `zk.str` configuration name is pretty meaninless and doesn't help with understanding.

I imagine comitting to a consistent pattern among the launcher script commands would help: require `-zkAddress` on all types. Additinally, I imagine having a clear config value that is consistent for all of them, eg `zookeeper.address` (making the config agnostic of `controller` vs. `broker` vs. `server`)

Start by comparing the launcher commands and configuration handling for brokers, servers, and controllers, focusing on -zkAddress, -configFileName, -clusterName, and the related configuration keys. Done means the node types follow a documented, consistent pattern for ZooKeeper and cluster configuration, with clear naming for the relevant config values.

Written by the indexing model from the issue text.