Acquire the GIL before creating a py::bytes objects in callbacks

[nomenquis]

The constructor of the py::bytes objects runs before the GIL is automatically acquired by the wrapped callback. So we have to make sure to acquire the GIL ourselves before, otherwise we'd run into corruption since PyMem_Malloc and friends are not thread safe.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}