Measure used memory

[l0rinc]

Previously we've measured the memory consumption for every received block, but ideally we'd instrument the binary similarly to how we do it with perf to make sure the peaks and trends are also captured.
We can likely do that with valgrind as long as they play nice with perf. This would be for an instrumented run, we can't rely on the speed characteristics of an instrumented run, but it shouldn't affect the flame graphs significantly.
This should help us understand any memory changes of any PR (e.g. bitcoin#30039 or bitcoin#31645)

[l0rinc]

This is how we're measuring memory for a full IBD (cc: @Eunovo):

# apt update && apt install -y valgrind
COMMITS="998386d4462f5e06412303ba559791da83b913fb 5cefc4bbadaa06f22089dd7991fac17ed5b283ca"; \
STOP_HEIGHT=888000; DBCACHE=1000; \
C_COMPILER=gcc; CXX_COMPILER=g++; \
DATA_DIR="/mnt/my_storage/BitcoinData"; \
LOG_DIR="/mnt/my_storage/logs"; \
mkdir -p $LOG_DIR; \
for COMMIT in $COMMITS; do \
  git fetch --all -q && git fetch origin $COMMIT && git log -1 --oneline $COMMIT && \
  killall bitcoind || true && \
  rm -rf $DATA_DIR/* && \
  git checkout $COMMIT && \
  git clean -fxd && \
  git reset --hard && \
  cmake -B build -DCMAKE_BUILD_TYPE=Release -DENABLE_WALLET=OFF -DCMAKE_C_COMPILER=$C_COMPILER -DCMAKE_CXX_COMPILER=$CXX_COMPILER && \
  cmake --build build -j$(nproc) --target bitcoind && \
  ./build/bin/bitcoind -datadir=$DATA_DIR -stopatheight=1 -printtoconsole=1 || true && \
  valgrind --tool=massif \
    --massif-out-file="$LOG_DIR/massif-$COMMIT-$STOP_HEIGHT-$DBCACHE.out" \
    ./build/bin/bitcoind -datadir=$DATA_DIR \
    -stopatheight=$STOP_HEIGHT \
    -dbcache=$DBCACHE \
    -blocksonly=1 \
    -printtoconsole=1 && \
  cp $DATA_DIR/debug.log "$LOG_DIR/debug-$COMMIT-$STOP_HEIGHT-$DBCACHE.log" && \
  ms_print "$LOG_DIR/massif-$COMMIT-$STOP_HEIGHT-$DBCACHE.out" | tee "$LOG_DIR/massif-$COMMIT-$STOP_HEIGHT-$DBCACHE.txt"; \
done

We can use the https://github.com/KDE/massif-visualizer to visualize the results instead of the ms_print ascii art

[l0rinc]

The memory usage could also have differential flame graphs - that would be very useful!