Configuration file includes full paths to UMM-G directory and CNM directory, not a separate base path.

[juliacollins]

Currently the .ini files include a local output directory value and a ummg_dir value representing a subdirectory in local_output_dir. For example:

local_output_dir = output
ummg_dir = ummg/nsidc-0081

No cnm_dir is defined for the cases in which CNM message content is written to file(s) as well as posted to a Kinesis stream. (We assume cnm exists as a directory in local_output_dir). Modify the .ini file content to look something like:

ummg_dir = output/ummg/nsidc-0081
cnm_dir = output/cnm/nsidc-0081

The user could be prompted for an output directory base name which is then glued onto the directory-only answers received for ummg_dir and cnm_dir -- or we could simply expect operators to type the whole path for each of ummg_dir and cnm_dir. Some input from @afitzgerrell is needed to verify the approach most useful for Ops.

Acceptance criteria:
Given: Interactive command-line option to quiz user for config file values
When: User runs metgenc --init
Then: The user is quizzed for output file locations according to Ops feedback, and the resulting .ini file has an entry for ummg_dir and cnm_dir but NOT local_output_dir.

Note that cnm_dir would only be required if the user wants to write CNM files in addition to posting the content (that is, if write_cnm_file is True).