cmake: fix FOLDER structure for IDE's that support it

[nilason]

Fix FOLDER structure for IDE's that support it (e.g. Xcode and MSVS).

This is a low-risk, coarse clean up of the folder structure, generating a tree like:

There is plenty of work to do on this end, but that will be for future pull requests.

Would be good to have this for 8.5.

[wenzeslaus]

This split Python/Tools (scripts) vs Tools/Temporal (temporal) does not make sense. The situation in the source code is not ideal (temporal scripts versus all the other scripts), but this adds another layer of unclear.

A quick fix perhaps would be Python/Other Tools (scripts) and Python/Temporal Tools (temporal).

[nilason]

This split Python/Tools (scripts) vs Tools/Temporal (temporal) does not make sense. The situation in the source code is not ideal (temporal scripts versus all the other scripts), but this adds another layer of unclear.

A quick fix perhaps would be Python/Other Tools (scripts) and Python/Temporal Tools (temporal).

Python tools are divided into subfolders (Python/Tools/Raster etc), just as compiled tools. We may eventually merge the two (just one Tools folder), but currently the Python files does not show in IDE (just as header files are missing), so I’d say it is better to separate them for now.
How about putting Python tools in one and the same Tools folder but still separate sub-folders: Tools/Raster (Scripts) or Tools/Raster (Python)?

[nilason]

Could this be a better (interim) solution?:

As I mentioned above, there's a lot to do with regards to IDE support, but this is a tremendous improvement to the current state.

[wenzeslaus]

All under Tools makes sense to me. I would go with Raster Script rather than Raster (Script), but then I don't know what to do with the Binary (not that I would be so sure about "Binary (Scripts)").

[nilason]

All under Tools makes sense to me. I would go with Raster Script rather than Raster (Script), but then I don't know what to do with the Binary (not that I would be so sure about "Binary (Scripts)").

Well the content of "Binary" and "Binary (Script)" is all the binary targets, which are not Tools:

It will take some work to sort that out, together with "the rest". Let us not dwell on details in an iteration of a WIP that does not affect GRASS as such.