las3_pub / predictable_parallel_patterns

We do so by pulling out the profiling macros in our own iclude file. In the future we might even be able to use this to build up further visualisations of the executing programm.

There are serval ways we could optimize the calls, but for now this should be enough for first tests.

This requires the user to explicitly manage the storage duration/place of the thread local state, making a fine grained memory allocation simpler.

We force linker errors if the new operator is used somewhere. See NOTES.md for details.

Seperate library from other parts of project (samples, playground, testing, ...). We still are in one 'toplevel' cmake project, so we can for exmaple compile everything (library and playground) in debug mode, for simple development.