Matt ayman frames

Redo of the merge of Frame, RigidFrame, FixedFrame, Station and Marker ModelComponents along with code to convert Marker to new format for serialization/deserialization and inclusion of FrameSet in model.
@sherm1 @msdemers @aseth1 or @chrisdembia Please review and let us know your feedback.
@aseth1 In that case, you want to create a new type of Frame, not a new type of RigidFrame, inside your shoulder model.  The reason for making RigidFrame was to identity a subfamily of Frames that connect rigidly to a Body.  They are to serve as frames of reference for the model to attach useful, physical stuff.  The point of making the RigidFrame subfamily was so modeling connections could be of defined type, connector<RigidFrame>, and guarantee that model component connected to is was actually connected a Body.  

It sounds like IntermediateScapuloThoracicFrame doesn't fit that standard.   Frame is modeling convenience in OpenSim's modeling API.  Those, especially RigidFrames, make sense when defined relative to OpenSim's modeling representation of Body.  Simbody doesn't have a distinction between bodies and frames, so worrying about generality of RigidFrames to work with intermediate Simbody components in the intermediate shoulder doesn't make sense to me.  You can still make SimTK::Transoforms if you're primarily working with Simbody internally.