Relax CMakePresets.json fixed location

The relatively recent introduction of CMakePresets.json and CMakeUserPresets.json are very appreciated here, but will require in our opinion an additional level of flexibility:

We would like create the files on the fly. While this is not that problematic for our Jenkins builds (checked out repos are deleted anyway afterwards), for local builds there should be the possibility to choose a user-defined path for the files (effectively putting/creating them in the build directory or out-of-source in general).

We could of course skipping things completely by creating / reading some self-defined json file and utilizing cmakes native json string support, but would lose all the semantic meanings of the both files.


Cc: @kyle.edwards

Issue 21331 contains discussions around this topic.