dunecontrol handling of cmake/configure options partially broken

While working on the CMakePresets.json generator #372 I observed that there are a couple of inconsistencies in the handling of parameters for cmake/configure.

configure is intended as an alisa for cmake, but when reading configurations from the $DUNE_OPTS_FILE the behaviour is to some extent inconsistent.

  1. it used different flags when running dunecontrol configure (CMAKE_FLAGS and CONFIGURE_FLAGS) and dunecontrol cmake (only CMAKE_FLAGS) $\rightarrow$ made consistent
  2. the CMAKE_MODULE_PATH was added to the cmake flags, but not read from the opts file $\rightarrow$ read from opts file if present
  3. additionally -DDUNE_OPTS_FILE=\"$DUNE_OPTS_FILE\" was added to the cmake flags, but only when calling dunecontrol configure $\rightarrow$ works now with configure and cmake

We either need to cleanup this opts-file handling or simply remove/deprecate the command configure.

Edited by Christian Engwer