fix: In concurrent situations, token similarity leads to multiple loc…

[jefferyjob]

In concurrent situations, token similarity leads to multiple lock acquisitions

The reason for this problem is that my current code implements a "reentrant lock" itself. The token automatically generated by the reentrant lock is based on the nanoseconds of time.Now().UnixNano(). The nanoseconds obtained in multiple concurrencies are consistent, resulting in the passive selection of the reentrant lock for lock counting.

close #24

[jefferyjob]

当前生成的 token 是基于 google/uuid 包实现的唯一ID生成。