Trajectory Optimization

This is not really intended as "ready to accept," but I wanted to start the conversation on trajectory optimization. I added (what I hope is) a pretty flexible framework for direct methods for traj opt, along with some implementations for some first-order integration schemes and direct collocation. The code is far from being speed-optimized, and I think one of the important discussions should be on how to prevent repeated, unnecessary calculations, similar to what Hongkai has with kinsol for inverse kinematics. 

I also added a ConstraintManager class, which is just intended to be a general interface for combining multiple constraints into one. I think this would be a good approach to describe more complex constraints, like support polygons and complementarity constraints.
Per the suggestion above, it seems more natural to have a constructor which just takes the bare minimum (p,N,T_span), and then the user populates with calls the different costs and constraints.  That seems like it would be more readable / natural to me.  (otherwise the NonlinearConstraint lines above are pretty obtuse)