SetupTrajectory.hpp related issue to #401

This issue is somewhat related to #401 since we can see that out of the box there are some limitations to the way the setup files have been built.

In SetupTrajectory.hpp the standard use case is the following: typedef corsika::tracking_line::Tracking Tracking; and typedef StraightTrajectory Trajectory; This already limits our examples to have straight trajectories for examples.

For radio where we need a magnetic field as well one has to use the LeapFrogTrajectory and tracking_leapfrog_curved. So in the SetupTrajectory.hpp one has to explicitly tweak the file and use the following if they want to use something other than StraightTrajectory like so:

typedef corsika::tracking_leapfrog_curved::Tracking Tracking; and typedef LeapFrogTrajectory Trajectory;

So, regarding this and issue #401:

These setup files for environment and trajectory etc. are somewhat cumbersome the way they are right now and I suspect we would have to rethink a more general implementation.