Initially connected member termination causes an inconsistent state

**Scenario:**
There are running members in the same cluster at ports 5701, 5702 and 5703 then default smart-client connected to those members. It first receives the member information from the first member that it is connected which is 5701 in this case. Then, connect all the remaining members via those information by listening certain event. After the client is ready, If we just terminate first member which is exploited for the discovery purpose through remote-controller, we just receive MembershipStateRemoved event as it is suppose to be. But when we attempt to add a new member through rc again, client does not receive MembershipStateAdded event. Rather, if we first remove the member which is discovered after the first member connection and add a new member again, rc works fine and throws MembershipStateAdded event. I tested both cases manually without the remote-controller in localhost, everything works fine as it is expected.

Gist: https://gist.github.com/nevzatseferoglu/37199fd3e2bcd7aa1cbdadc5843a2f5d
Slack discussion: https://hazelcast.slack.com/archives/C016TGXPWPJ/p1656085097529409