Unifying data type usage for trip models in e-mission-server and e-mission-eval-private-data repositories

[humbleOldSage]

In the trip modelling on e-mission-server repository, the predominant data type we are working on is the Entry type.

Conversely, the labeling of trips on e-mission-eval-private-data repository primarily utilizes dataframes, though it also incorporates Entry type data to some extent.

To enhance code base consistency and simplify development, we can standardize on a single data type - either data frames or Entry types - across both repositories. Alternatively, if a mixed of Entry and data frames remains necessary, all utility functions should support both data types.