Add clang format from samples repo

[SaschaWillems]

As noted in #126 code style is all over the place, making things hard to read.

We should start using a clang format file like we did in the samples to make sure code style follows a fixed set of guidelines.

This PR is there to discuss that. It adds the clang format file from the samples and applies that to one chapter.

We prob. still would have to do at least some manual fixups, as even clang format can't get everything into a good-to-read shape. But it should do hopefully around 90% of the job.

While modern C++ is generally hard on the eyes, this makes it at least somewhat easier to read and (more importantly) more consistent.

[asuessenbach]

Besides lots of other settings I'm using with the Vulkan-Hpp project, something like
ColumnLimit : 160
helps very much in getting some nice formatting, preventing arbitrary long lines.

Just for reference, I've attached the clang-format from Vulkan-Hpp as a text file: clang-format.txt

[SaschaWillems]

As agreed on the last call: I'll apply the clang format to all files and update this PR.

[SaschaWillems]

No idea why the Android build fails.

[asuessenbach]

No idea why the Android build fails.

clang_format has sorted the includes. Now, vulkan_android.h is included before vulkan_core.h in 34_android.cpp.

[SaschaWillems]

Oh, that was prob. stupid. Will redo this PR without reordering the includes :/

[asuessenbach]

Oh, that was prob. stupid.

No, that was not stupid. It's vulkan, that is stupid.
I would prefer to just exclude those two #includes from reordering/formatting.

Or maybe just #include <vulkan/vulkan.h>, instead.

[SaschaWillems]

That would be the better option. Didn't realize that the tutorial did explicitly include the core/platform specific headers. That indeed does not make much sense and should be changed indeed. Also feels odd that every chapter explicitly includes "vk_platform.h".

[gpx1000]

looks like merge conflicts. Could you address?