feat(command): add a new command to enable/disable/dump the memory profiling

[git-hulk]

This closes #3006.

Currently, it's hard to identify where's occupying the memory when it goes high.
To mitigate this issue, we would like to introduce a profiling command to make the
process easier.

To enable this feature, you need to set the MALLOC_CONF environment variable before running the Kvrocks server, like the following instruction:

$ export MALLOC_CONF="prof:true,background_thread:true"
$ ./kvrocks -c kvrocks.conf

or

MALLOC_CONF="prof:true,background_thread:true" ./kvrocks -c kvrocks.conf

You could also enable the profiling feature without activating the profiling behavior to avoid the overhead:

MALLOC_CONF="prof:true,prof_active:false,background_thread:true" ./kvrocks -c kvrocks.conf

You can then enable it at runtime if necessary:

## Enable the memory profiling, set prof_active to true.
$ redis-cli> KPROFILE MEMORY ENABLE

## Inspect the profiling status
$ redis-cli> KPROFILE MEMORY status

## Dump the profiling file into /tmp directory, which named with `jeprof_` prefix.
$ redis-cli> KPROFILE MEMORY DUMP /tmp

## Disable the memory profiling, set prof_active to false.
$ redis-cli> KPROFILE MEMORY DISABLE

[sonarqubecloud]

Quality Gate failed

Failed conditions
41.7% Coverage on New Code (required ≥ 50%)

See analysis details on SonarQube Cloud