Add ability to filter out based on speed or jump during actel explore, migration, or residency

[dsmith-unbc]

Actel currently has a jump.warning / jump.error and speed.warning / speed.error to help clean the data and identify possible issues. I would like to recommend a jump.removal and speed.removal be added.

For example, if speed.removal is set to 2.5m/s, any observation which travels faster than 2.5m/s between one station and the next would be discarded from the data. The same would be said for jump.removal where if this is set to 3, observations which jump 3 stations since the last observation would be discarded instead of throwing an error or requiring user interaction.

This would allow filtering of large datasets to go faster and enable the speed and jump functions of actel to be utilized on high performance computing clusters, such as Compute Canada, where user interaction is not possible once the code has been pushed to the clusters.

Observations filtered out by speed.removal and jump.removal should still be appended to the bottom of the actel report along with a summary of how many observations were removed by the process.