Adds tests to check if PersonCostEvents match their expected trip costs#3760

Draft

HoneyTauOverTwo wants to merge 3 commits intodevelopfrom 3746-incorrect-pattern-matching-in-personagent-current-trip-cost

+287-43

Commits on Jul 12, 2023

Adds test to check if PersonCostEvents match the expected trip cost calculated by using their respective PathTraversalEvents.
HoneyTauOverTwo
committed
Adds fix to issue #3746 . PersonAgentTripCostTest is flaky at this stage meaning there are other sources for cost discrepancy.
HoneyTauOverTwo
committed
Changes "EmbodiedBeamLeg.splitLegForParking" (source of another cost discrepancy) and "currentTripCosts" from "BasePersonData":
HoneyTauOverTwo
committed