Add position_point parent class

Currently there are multiple ways to define a position point in OSC2 (and there will be more such as GPS positions, lanelet points, etc).

I would suggest to add some parent class, because it could simplify a lot of interfaces. (Naming to be defined!)

With this we could simplify following actions and methods without breaking the API and be open in future for further point definitions (without the need to extend the interfaces):

1. assign_position: Suggestion: add parameter position_point, so we can pass also GPS positions for example (Or further costume position definitions) https://www.asam.net/static_downloads/public/asam-openscenario/2.0.0/domain-model/actions.html#sec-actions_movableobjects-class-assign_position

1. distance_to_point: Suggestion: add parameter position_point, so we can pass also GPS positions for example (Or further costume position definitions) Here we currently would need to add three methods (and do that for each new position definition) #762 (closed)