chore(deps): use cuid2 instead of cuid

[yoshinorin]

Why

https://github.com/paralleldrive/cuid has been deprecated and we have to use https://github.com/paralleldrive/cuid2 instead.

Breaking change?

I assume warehouse uses cuid to generate post id. So, all of the post ids in db.json will be changed if we merge this PR. I think the posts ids are not on the premise that permanently stored (If hexo has to store ids permanently, should use RDB). But this change may be a breaking change for some users if they are using any plugin and it depends on that premise.

---

Closes: #146

[yoshinorin]

Hmm... We have to fix TS2362 & TS2322 errors before submit this PR.

[yoshinorin]

I can't reproduce TS2362 & TS2322 errors locally...

[yoshinorin]

Blocked by: #148

[yoshinorin]

Ready

[SukkaW]

cuid is indeed deprecated, but I don't see any reason to upgrade to cuid2. warehouse doesn't rely on cryptographic safety

[yoshinorin]

cuid is indeed deprecated, but I don't see any reason to upgrade to cuid2. warehouse doesn't rely on cryptographic safety

Yes. We can suspend migrating from cuid to cuid2 until we really needed. (e.g. cuid does not work with Node.js v20)
I convert this PR to draft.

Thanks

[SukkaW]

Yes. We can suspend migrating from cuid to cuid2 until we really needed. (e.g. cuid does not work with Node.js v20) I convert this PR to draft.

Also ideally, we should consider migrating to a more performant id generation (instead of sticking with the cuid). warehouse is basically a database, and we can choose basically any safe random id generator we want.

Let's run a benchmark on cuid, cuid2, https://www.npmjs.com/package/uid, and https://www.npmjs.com/package/nanoid, so we can find out the fastest one.

[D-Sketon]

a simple benchmark with https://github.com/ai/nanoid/blob/main/test/benchmark.js

cuid2                         42,848 ops/sec
nanoid                     4,442,592 ops/sec
cuid                         154,202 ops/sec

Non-secure:
uid                       65,298,000 ops/sec

[stevenjoezhang]

Considering their performance and maintenance (update frequency), I think nanoid is a good alternative option. I will attempt to migrate to it.

Superseded by #244