Avoid conflict in queue join, e.g. same name

[andrewsoonqn]

Current frontend logic is to use name entered + time entered to create a unique id. There might (although unlikely) be cases where people of the same name join at the same time.

Possible implementation:

• current implementation of JWT tokens embeds userId given by Telegram, which allows us to uniquely identify different users
• this issue will probably be solved once we integrate with database

[Jax0312]

Can confirm the queue join logic is soundly handled by the backend. Frontend only needs to make a post request to /queue/entries