If no problem type is specified in .config file, "EISMINT" error occurs

_From @matthewhoffman on July 28, 2015 15:23_

If no problem type is specified in the .config file, CISM aborts with:
`FATAL ERROR : No EISMINT forcing selected`

There is no documentation for how a user should set up a user-defined simulation that is not one of the canned test cases. The modules that parse the .config file look for different domain types as a config section in square brackets. For instance, an EISMINT-2 test has a [EISMINT-2] section (with some items beneath it), a dome test has a [DOME-TEST] section (with no items beneath it). Currently the code is expecting one of these problem types to be specified, and if one isn't then it throws the error "FATAL ERROR : No EISMINT forcing selected".

A workaround for running a user-defined problem is to add the line:
`[DOME-TEST]`
to the .config file. The dome test is a generic problem type and can be used for any user-defined simulations. This line simply tells CISM that nothing special needs to occur in setting up the problem. Ideally we should generalize this so that for a generic problem either
1) no problem type needs to be defined at all; or
2) we have something like a `[GENERIC]` problem type that makes it explicit that nothing unusual needs to occur inside the model set up.

_Copied from original issue: E3SM-Project/cism-piscees#38_