Alternative interplay between dunecontrol and cmake

Currently the only easy way to call cmake is via dunecontrol, as we need to pass all the different dependencies to cmake and only dunecontrol "knows" where to find hthe other modules.

This became really annoying when I started playing around with vs-code, as the it wanted to run cmake from within vs-code.

I propose to change the way dunecontrol and cmake play together, so that it doesn't call cmake with many many many arguments any more, but instead writes all these arguments to an additional file, which can be used by cmake.

I investigated the situation a little bit and one option would be to use the presets of cmake. dunecontrol could write a CMakePresets.json which includes all the path information as a list of additional "cacheVariables". What do the cmake experts think?