The checkOnlineRegionsReport can accidentally complete a TRSP

On our testing cluster, we observe a race condition:
1. A regionServerReport request is built
2. A TRSP is scheduled to reopen the region
3. The region is closed at RS side
4. The OpenRegionProcedure is created
5. The regionServerReport generated at step 1 is executed, and we find that the region is opened on the RS, so we update the region state to OPEN.
6. The OpenRegionProcedure notices that the region has already been in the OPEN state so gives up and finishes.
7. The TRSP finishes.
8. The region is recorded as OPEN on the RS but actually not, and can not recover unless we use HBCK2.