Issue#3 trajpt base class

There are still no methods for actually setting values, but this starts to build ideas and functionality we need. Fixes issue #3.
My feeling is that process data lives outside of this framework because it isn't required for planning. Each trajectory point contains an id_ member. Presumably, the actual application maps each of its own process points to a trajectory pt, and activates process information when the apropriate trajectory point is reached.