feat[code]: extend StatePoint

[denotte]

Reference to a related issue in the repository

#748

Add a description

Extends the StatePoint with optional fields velocity, acceleration, orientation and orientation rate.

Some questions to ask: What is this change? What does it fix? Is this a bug fix or a feature? Does it break any existing functionality or force me to update to a new version? How has it been tested?

Take this checklist as orientation for yourself, if this PR is ready for the Change Control Board:

• [X] My suggestion follows the style and contributors guidelines.
• [X] I have taken care about the message documentation and the fields and enums documentation.
• [X] I have done the DCO signoff.
• [ ] My changes generate no errors when passing CI tests.
• [X] I have successfully implemented and tested my fix/feature locally.
• [ ] Appropriate reviewer(s) are assigned.

If you can’t check all of them, please explain why. If all boxes are checked or commented and you have achieved at least one positive review, you can assign the label ReadyForCCBReview!

[lemmer-fzi]

As the StatePoint message is used in various other messages the inteded usage of the StatePoint message is documented in the respective messages. Therefore, the respective documentations (for example in TrafficCommand and MotionRequest) should be updated accordingly.