- changed to new JSON library (nlohmann_json)
- now uses correct folder for sketchup files
- Note: The test relies on a .skp file which is not available

First, use the CMAKE_RUNTIME_OUTPUT_DIRECTORY variable to get the configuration dependant output folder.
However, configure_file does not support generator expressions.
Thus switch to file(GENERATE).

Here, the required file has the same name as another file, thus, renaming it.

First, use the CMAKE_RUNTIME_OUTPUT_DIRECTORY variable to get the configuration dependant output folder.
However, configure_file does not support generator expressions.
Thus switch to file(GENERATE).

The Visual studio generator is a multi config generator.
This means, that form one project, e.g debug and release can be build.
This caused issues, as the default behaviour is to append the configuration type to the output directory.
Thus, dlls and required files were not copied to the right locations.

By adding the generator expression '$<Config>' to the CMAKE_RUNTIME_OUTPUT_DIRECTORY path,
the default appending behaviour is supressed and every configuration uses its own output folder.
The dlls and required files can then be copied in the correct folder for each configuration.

The use of 'using namespace std' caused compile error 'C2872:byte ambiguous symbol'.
This is caused as the c++ standard defined byte and an old windows header.
When 'using namespace std' is present, the compiler cannot differentiate the two.
Under normal compilation this is not a problem, however, pigeon uses QT and it uses std::byte.
As it is bad practive anyway, removing the using definition.

References:
https://stackoverflow.com/questions/60793009/error-using-qt-during-build-c2872-byte-ambiguous-symbol
https://studiofreya.com/2018/01/06/visual-studio-2017-with-cpp17-and-boost/#stdbyte-ambiguous-symbol-and-rpcndr.h

Perform the same steps as in ITABase previously:
- Use modern targets
- Update some functions
- Remove VistaCMakeCommon
- Improve installing

- Ray now has bools indicated whether it is an eigenray and whether accuracy as reached
- Booleans are set at end of EigenraySearch
- adjusted conversion functions accordingly

- now always traces new ray grid if eigenray is close to pole
- if eigenray points towards pole, now uses a circular grid with 5° azimuth resolution