Fix strict round robin cur_index increment

rr_next was wrongly casted as a int32_t instead of as uint32_t. As shown
on trafficserver#6321, on long-lived ATS instances the value of rr_next
would be interpreted as a negative value, it would be incremented till
the value reaches 0, hence all the traffic hits the first parent
1 file changed