Make server-side loggers individually configurable.

[glitch]

Currently the loggers on the arkouda_server are managed with a global configuration variable v defined in ServerConfig

Chapel allows config const values to be set via cmd line args such as --FooClass.v=true and we can take advantage of this feature to allow more customized logging configuration.

It may also be worth looking into a common log configuration format to allow groups of modules/classes to be turned on and off at once (i.e. something similar to how logback or log4j work... not the dynamic part, but the config file part). If we look at the (optional) config file the format should be something like yaml or json, and the order of override should be config file, overridden by command-line args.

[glitch]

Associating with Issue #757

[hokiegeek2]

Got this working. The default logging level is INFO. The first example is with arkouda_server (notice arkouda_directory debug message):

Second one is MsgProcessing debug:

And the third one is MsgProcessing warn: