Add -I $soaap_include_dir to regular C[XX]FLAGS.

We need the __soaap_foo() declarations in regular compilation, too.
Add some SOAAP vulnerability annotations to Chrome.
A simpler way to create a SOAAPy build.ninja.

To do the Capsicum SOAAP work, we need to regenerate Chrome's build.ninja file and then apply SOAAP changes to it. Rather than committing a particular build.ninja file to revision control (which will, among other things, hardcode a particular user's SOAAP path), let's commit a diff that can be used to patch Gyp-generated Ninja files.
Remove 'out' directory from revision control.

When we build with different options, we need to re-Gyp the Ninja files. Now that we have a /capsicum/soaap-ninja.patch, people should run './build/gyp_chromium --depth .' and then apply the patch to the build.ninja file.
Add the 'run-gyp' wrapper.

This wrapper does three things:
1. configures an environment like the one used by the www/chromium port,
2. runs Gyp and
3. patches the output Ninja files to use SOAAP.
Improve the 'run-gyp' script slightly.

Make the 'run-gyp' script check for $LLVM_BUILD_DIR and $SOAAP_SOURCE_DIR and patch them into the output build.ninja. Now there is absolutely no need for manual hacking of the build.ninja file!
Also ignore the 'out' directory.

Since this directory is no longer kept in revision control, Git can safely ignore it. This speeds up 'git status' quite a lot.
Merge branch 'master' into capsicum.