The mappings are a combination of useless, inaccurate, and harmful.
Leave them out until they are helpful and correct.

Fundamental issues:
 - If in need of mappings, a user would need HTTP -> gRPC code mappings.
   But the docs don't provide that since the mappings are not 1:1.
 - There _is no_ gRPC -> HTTP code mapping taking place in gRPC. This
   may change in the future, but until then the docs are misleading.

But even given those were resolved, there are additional issues. Two
obvious examples:
 - 501 Not Implemented is refering to HTTP methods such as GET and POST
   not being implement. That should not be used for gRPC methods not
   found (UNIMPLEMENTED).
 - 404 Not Found is for when the resource is not found. In gRPC, the
   resource is the gRPC method, not the parameters (NOT_FOUND). If there
   is a REST conversion layer on top of gRPC, then 404 would be
   appropriate, but that just shows that the mapping can not be
   canonical.

Fixes #898.

Adding support to enable tracing in tsi.

Update log_posix.c

This allows for easier scripting and updates.

size error

Guard headers tool.

Omit some tests, speed up others, prepare for ASAN

Suppressing a data race in OpenSSL

This race is (probably) legit on some platforms, but (likely) safe on Intel at least.
For now, since it's a little outside our control, I'm suppressing it to focus on any remaining races in our code.

Multithreaded Async C++ perf tests, plus gens rename of Async client methods

This reverts commit 45b0bc4b.

This revert is being done because the compilers on Travis don't
understand the C++11 template/using syntax.

Removing the ssh setup of the dockerfile.

Auth node test

Also speed up a test, and disable some rarely touched but long running tests

Update suppressions file

Added ruby tests to run_tests.py

Fix conditional inclusion of grpc_csharp_ext.dll

Removing private protobuf header inclusion.