Migrate to tikv-jemallocator

[jedel1043]

We are currently the jemallocator as a fast allocator. However, that crate hasn't gotten a release in 3 years. The official successor of that project is tikv-jemallocator, maintained by the TiKV project. We should migrate to that.

[Jayesh-Dev21]

Hi @jedel1043, I'd like to take this!

For #5516 it's a rename for jemallocator -> tikv-jemallocator (same Jemalloc API). I'll migrate the workspace dependency and update the allocator usage in cli/benches, then regen the Cargo.lock file and verify with cargo check/clippy.

Quick question -> should I keep it at 0.5.4 (rename-only, avoids dependency version risk) or bump to a newer 0.6/0.7 of tikv-jemallocator in the same PR? Happy to do either.

If a particular newer version of tikv-jemallocator is needed then we could discuss it

Setup is already done from my previous fix #5501 (fixes #5481, not merged yet 😢).

Working on this and will open the PR shortly!

---

Refer: tikv-jemallocator