add support for specifying builds by providing module name (WIP)

[boegel]

The idea here is to support installing software using eb by providing module names, rather than specifying easyconfigs, like:

$ eb OpenFOAM/2.3.1-intel-2015a
# corresponds to 'eb OpenFOAM-2.3.1-intel-2015a' when using default module naming scheme

or:

$ eb MPI/GCC/4.9.2/OpenMPI/1.8.4/FFTW/3.3.4
# corresponds to 'eb FFTW-3.3.4-gompi-2015a.eb' when HierarchicalMNS is used a module naming scheme

This would be one way of specifying what to install when 'fat' easyconfigs (e.g. GCC.eb or GCC.yaml) are installed, other ways may be added later (e.g., eb OpenFOAM 2.3.1 intel/2015, or eb <software name> <software version> [<versionsuffix>] <toolchain>)

TODO list:

• extend API for module naming schemes to support parsing of provided module name
• implement parsing of module names for EasyBuildMNS
• implement parsing of module names for HierarchicalMNS
• implement parsing of module names for other included module naming schemes
• add support to eb to also accept module names, and go find corresponding easyconfig file

[hpcugentbot]

Refer to this link for build results (access rights to CI server needed):
https://jenkins1.ugent.be/job/easybuild-framework-pr-builder/2000/
EasyBuild framework unit test suite PASSed (see https://jenkins1.ugent.be/job/easybuild-framework-pr-builder/2000/console for more details).

This pull request is now ready for review/testing.

Please try and find someone who can tackle this; contact @boegel if you're not sure what to do.