[Bug]: In release-v3.7, msg seq increase not use redis incr

[zshen-wish]

What would you like to share?

https://github.com/openimsdk/open-im-server/blob/release-v3.7/pkg/common/db/controller/msg.go#L385
Not use redis incr may cause some concurrency issue, or it is my misunderstanding?

Additional information

No response

[OpenIM-Robot]

Hello! Thank you for filing an issue.

If this is a bug report, please include relevant logs to help us debug the problem.

Join slack 🤖 to connect and communicate with our developers.

[FGadvancer]

For transfer consumption, coroutine sharding ensures session serialization processing, and it is handled in batches. Therefore, a set is used instead of incr.