refactors for clarity (and fix heuristic), O/D node index were unnecessary in arguments as we have the KPs in

TODO: find a more elegant way to do this, because it makes the Heuristic(s) responsible for updating a member of SAEVRoute
I could make it a member of BestInsertionHeuristic but then that means we have to instanciate an object to use the algorithms which seems inappropriate. Unless maybe if Heuristics classes ends up being delegate members of another class to allow heuristics/algorithms change via this delegate

add best insertions function with neighbour feasibility check function (TODO: test perfs wrt no feasibility checks)

Add InsertionStatus to changelists to properly insert/remove requests when applying/reverting changes

REFACTOR directly refer to insertion key points wherever possible to prevent any divergence in the kind of index expected by the function's implementation

WIP DEBUG add best request insertion queue to order possible insertions depending on score (TODO : debug detour score, use KeyPoints or appropriate indexes)