applying XENON100 --> LUX patch

This fixes a `undefined reference' build error with NMSSMTools 4.2.*
adding nmh_slhainp.f from Ulrich Ellwanger

This Fortran file will replace nmProcessSpec.f in the future.
We will keep nmProcessSpec.f for the moment for testing.
adding support for DR-bar parameters output scale in MODSEL entry 0

This feature was requested by Ulrich Ellwanger for the NMSSMTools
compatible SLHA output.  In NMSSMTools nmh_slhainp.f will read MODSEL
entry 0 and use the there defined scale to calculate the decays.
introducing debug flag entry 19 in Softsusy block

If entry 19 == 0, the old nmProcessSpec compatible output will
be printed.
If entry 19 == 1, the new nmh_slhainp compatible output will
be printed.
do not output MODSEL entry 0 in case nmProcessSpec is used
adding temporary SLHA input flags for testing nmh_slhainp.f
bugfix: NMSSMTools output scale is specified in block MINPAR

Remaining problem: the MINPAR entry 0 is printed in the EXTPAR block
because minparSLHA() prints both MINPAR and EXTPAR.  We need to
decompose minparSLHA() into two functions.
support nmh_shlainp.f mode in the softsusy_nmssmtools script
remove unused parameter (introduced in the previous commits)
use MINPAR entry 12 for the output scale choice (instead of entry 0)

According to SLHA 1, MINPAR entry 12 defines the output scale of the
DR-bar parameters.  MINPAR entry 0 is not defined in SLHA.
ensure output scale entry 12 appears in the MINPAR block
reading entry 12 from block MODSEL (instead of MINPAR)

This fixes a mistake I made before: SLHA defines entry 12 in block
MODSEL, not MINPAR!
optimization: avoid frequent flushing
Merge branch 'master' into nmssmtools-interface
clean up NMSSMTools interface

removing src/nmProcessSpec.f
Merge branch 'master' into nmssmtools-interface
adding micrOMEGAs output in 'omega' to the SLHA output file
commenting micrOMEGAs flags in the NMSSM SLHA input files
replacing nmh_slhainp.f by U. Ellwanger's first cleaned-up version

Note: I removed the reading of EXTPAR entry 0 and MINPAR entry 0,
because it leads to a wrong Q2 scale.
bugfix: setting VFLAG from VAL, not from IVAL

This was a copy-and-paste error.  When we arrive at block MODSEL, we
read IX and VAL, but not IVAL.