crimson/net: enforce strict reset/accept order

crimson/net: enforce strict reset/accept order

When a new connection tries to replace the old one, the event order
should be like:
1. reset(old);
2. accept(new);

This means we cannot just reschedule the reset event asynchronously. And
we still need to make sure the internal state is integral when reset.

Signed-off-by: Yingxin Cheng <yingxin.cheng@intel.com>