feat[code]: extend DetectedMovingObject with estimated trajectory

[denotte]

Reference to a related issue in the repository

751

Add a description

This proposal adds repeated StatePoints to the message DetectedMovingObject to describe an estimated future trajectory of this entity.

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:

• My suggestion follows the style and contributors guidelines.
• I have taken care about the message documentation and the fields and enums documentation.
• I have done the DCO signoff.
• My changes generate no errors when passing CI tests.
• 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!

This pull request is planned to be discussed in the Subgroup Other Models & Harmonization Joint Meeting 17.12.2023.

[thempen]

Comment from OSI Workgroup Other Models:

• Change the documentation for StatePoint according the coordinate system. It is not global coordinate system in this message.
• The estimated trajectory to be introduced should be within the CandidateMovingObject to have different trajectory estimation for different traffic objects (e.g. cars, or trucks).

[yash-shah-asam]

ASAM OSI CCB 2025-04-10: A working group is needed to work on this.