Api-incremental: copy RT for deviations

Requested by the client, this patch solve the issue until solved at the origin of data. On deviations, the previous RT needs to be copied to the new deviated trip.

This is performed by using a suffix, used only for deviations and allowing to search for the previous trip when a deviation is created/activated/deactivated.

The deviation follows a possibly different path than the original trip, thus, the RT is copied only up to the first stop with a different scheduled time, which is supposed to be the first deviated stop. From this point, no RT is copied. An improvement could detect similar stop-points and make a diff to apply RT after the deviation, but it usually has little added value.