raop: fix sequence number overflow

Shift back to the initial sequence number when we reach uint16_t's max
0xFFFF. This avoids asserting in pa_raop_packet_buffer_get().
I've chosen to shift back to the initial sequence number instead of 1
because 1 somehow triggered a flood of UDP timing packets.