patch_all() is unsafe

There is a bit of ambiguity of `patch_all()` approach on `aws-xray-sdk-python`. Use thereof automatically enables new patchers regardless to how well they've been tested against real use cases (https://github.com/aws/aws-xray-sdk-python/issues/48, https://github.com/aws/aws-xray-sdk-python/issues/90). This in turn can can lead to a nasty surprise where deployment of lambda function will not work as it patches the calls.

Some ideas on making the situation better:
1. Discourage use of `patch_all()`due to its unsafe nature.
2. Do not include new patchers in `patch_all()` outside of major versions
3. Split `patch_all()` into two functions `patch_all()` and `patch_all_bleeding_edge()` where new, and un-vetted patchers are first introduced into `patch_all_bleeding_edge()` and after they've been tested are then introduced to `patch_all()`

まず Python SDK の実装と patch_all() の呼び出し元を特定し、次にリンクされている issue #48 と #90 を読み、ここで説明されている Lambda のデプロイ失敗を検証します。完了とするには、新しい patcher に対する maintainer 選定のポリシーと、合意された API または動作の変更が必要です。この issue ではファイルやテストは指定されていません。

索引モデルが issue の本文から書いたものです。