rtpsource: Don't store invalid running times and calculate with it

If we end up with GST_CLOCK_TIME_NONE as running time for an RTP packet then this can't be used for bitrate estimation, and also not for constructing the next RTCP SR. Both would end up with completely wrong values, and an RTCP SR with wrong values can easily break synchronization in receivers.

Merge request reports