Hi all. I noticed that the behavior of go client Seek is different with Java client, which may confuse the users.
More details here: https://github.com/apache/pulsar-client-go/issues/919. Overall, if go client executes `Seek(id)`, it will reset its position in `id` instead of `id+1` by default. It's different with Java Client. I think we should modify it to make sure that Go Client `Seek()` has the same behavior with Java Client. Even though it will bring the breaking change. Please feel free to leave your comments. Thanks, Jiaqi Shen
