fix: newToken work under http

[tmtmtoo]

#12

During development, there are cases where next.js is accessed over HTTP.
Since browsers cannot use crypto.randomUUID() with HTTP connection, it should fallback to other methods of random number generation, such as Math.random().

https://developer.mozilla.org/en-US/docs/Web/API/Crypto/randomUUID

[valeryq]

@ypresto Hi, can we merge it, please? NextJS supports Safari 12+, but crypto.randomUUID support started only from Safari 15.4, we need earlier support than 15.4.

[ypresto]

@tmtmtoo Thank you! We do not need to call crypto.randomUUID() because Math.random() must be always available despite of environment.

[tmtmtoo]

@ypresto Thank you for the review. If a simple random string is sufficient as the token specification, how about the implementation in 95a023b?

[peinguin]

@ypresto , could you, please, take a look at the PR?

[Tamicktom]

Nyaa~~ (≧ω≦)/

Im getting the same error here when testing on a server using HTTP! 🖥️🌐✨ @ypresto senpai, could you pwetty please take a look at this PR? UwU🌸💕

Arigatooo~ 🎀✨