Issue with passing trace_entity when using ThreadPoolExecutor in lambda

I followed the instructions in the readme for passing the trace entity in a ThreadPoolExecutor but this does not appear to work properly in a lambda. The first time a thread does some work the trace_entity does not stick and the subsegment gets put under the root node not the one it should be assiciated with. The next time a thread picks up a job everything seems to operate fine.

I dug into the code a bit and it seems like there is a custome context class for lambdas but it does not override `set_trace_entity` to work properly with the other changes in the class. To workaround the issue I have found calling `get_trace_entity` before setting sets the internal state up properly.

example workaround from readme
```
def load_url(url, trace_entity):
xray_recorder.get_trace_entity() # Workaround to setup internal state
xray_recorder.set_trace_entity(trace_entity)

resp = requests.get(url)

xray_recorder.clear_trace_entities()
return resp
```

Comienza con el ejemplo de ThreadPoolExecutor del README e inspecciona la clase de contexto personalizada utilizada para las lambdas, especialmente cómo se inicializan y establecen las entidades de traza. Reproduce el primer trabajo gestionado por un hilo y verifica que su subsegmento se adjunta a la entidad de traza proporcionada sin necesidad de una llamada previa a get_trace_entity.

Escrito por el modelo de indexación a partir del texto del issue.