Refactor serialization mechanism to be extendable

At the moment, our serialization code is just a really long `if-elif-elif-...` block: https://github.com/elastic/apm-agent-python/blob/ee45d21ff43be495089a005863b7f6af0707fe34/elasticapm/utils/encoding.py#L85-L138.

This has several drawbacks:
* it's not extendable (we e.g. might want to serialize Django `QuerySet` objects in a sane way that doesn't evaluate the queryset unnecessarily, but only if Django is installed)
* it's brittle
* it's hard to read
* ideally, serialization would also include shortening of values, which is hard to do in its current state

One option could be to have a registry, to which transformers can register themselves, together with a list of supported types for that transformer.

首先阅读 elasticapm/utils/encoding.py 中第 85-138 行附近的内容，目前序列化是在那里以一长串条件链的形式实现的。将提议的 registry 方案与可选处理 Django QuerySet 以及缩短值的需求进行比较。当序列化机制具备可扩展性、更加稳健，并且在安装 Django 时避免不必要地对 QuerySet 求值，即可视为完成。

由索引模型根据 Issue 内容生成。