Allow pickling of `TransferTrajectory`

[Pocket-titan]

Hi!

I noticed that a lot of the examples using pygmo for optimization have to rely on some "hacks" (re-initializing the object for every thread: can be expensive and clunky) (one, two) to make the object pickle-able so the optimization can be parallelized. The fundamental issue as I understand it is the TransferTrajectory class: cloudpickle can't pickle this, and for me the lambda trick also doesn't circumvent this.

However, pybind11 offers pickling support if you define the appropriate methods on the C++ side. Is this something that's maybe desirable?

[DominicDirkx]

This would definitely be good to have, we just have not yet gotten around to it yet :) Can you explain why the lambda trick does not circumvent the issue in this case?

[DominicDirkx]

While interesting, we do not foresee being able to allocate any development capacity to this issue in the near future, and are closing it.