Ack/Nack use closed consumer

#### Expected behavior

1：use Client to Subscribe a topic create an consumer-1
2：Receive message use consumer-1
3：then in some case consumer-1 is Closed.
4：use the same Client to create another consumer-2 to Ack/Nack the message

expect consumer-2 to Ack/Nack the message

#### Actual behavior

the Ack/Nack will use consumer-1 which is Closed before.

Tell us what happens instead

#### Steps to reproduce

1：use Client to Subscribe a topic create an consumer-1
2：Receive message use consumer-1
3：then in some case consumer-1 is Closed.
4：use the same Client to create another consumer-2 to Ack/Nack the message

#### System configuration
**Pulsar version**: x.y

Start by reproducing the listed consumer-1 and consumer-2 sequence in the Go client; the issue names no files or tests. Trace how a received message is associated with a consumer when Ack/Nack is called after the original consumer closes. Done means Ack/Nack uses consumer-2 rather than the closed consumer-1.

Written by the indexing model from the issue text.