Use jemalloc to trace thread allocation

[CalvinNeo]

What problem does this PR solve?

Issue Number: close #8835, close #8589

Problem Summary:

1. WITH_JEMALLOC to enable external-jemalloc
2. Introduce reportThreadAllocInfo etc.

Basicly two modes:

1. For everlasting threads, record allocated/deallocated ptr, update according to these ptrs.
2. For non-everlasting threads, mostly comes from Proxy, update only when the thread is executing something.

We don't directly monitor at FFI boundary because:

1. There are some threads like raftstore which can't be monitored through FFI boundary.
2. Rust's thread id does not has a meaning.

See also https://github.com/pingcap/tidb-engine-ext/pull/366/files

What is changed and how it works?

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
• No code

Side effects

• Performance regression: Consumes more CPU
• Performance regression: Consumes more Memory
• Breaking backward compatibility

Documentation

• Affects user behaviors
• Contains syntax changes
• Contains variable changes
• Contains experimental features
• Changes MySQL compatibility

Release note

None

[CalvinNeo]

[JinheLin]

This filename is easy to confuse with MemoryTracker.cpp.

[CalvinNeo]

Changed into MemoryAllocTracker

[CalvinNeo]

/run-all-tests

[CalvinNeo]

/unhold

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: JaySon-Huang, JinheLin, Lloyd-Pottiger

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [JaySon-Huang,JinheLin,Lloyd-Pottiger]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[CalvinNeo]

[2024-03-18T09:33:57.596Z] 
Stopping fullstack-test_tiflash0_1 ... error

Stopping fullstack-test_tikv0_1    ... error

Stopping fullstack-test_pd0_1      ... error

Stopping fullstack-test_tidb0_1    ... done


[2024-03-18T09:33:57.596Z] ERROR: for fullstack-test_tiflash0_1  cannot stop container: 1f118e0614d4aac39cf246135f74a693a79197d56bb4142de62f0999daa734ca: tried to kill container, but did not receive an exit event

[2024-03-18T09:33:57.596Z] Removing fullstack-test_tidb0_1    ... 

[2024-03-18T09:33:57.596Z] Removing fullstack-test_tiflash0_1 ... 

[2024-03-18T09:33:57.851Z] 
Removing fullstack-test_tidb0_1    ... done

Removing fullstack-test_tiflash0_1 ... done
Removing network fullstack-test_default

[2024-03-18T09:33:57.852Z] error while removing network: network fullstack-test_default id c8d1b8608346fbdb325d6157808b9a71ad112ff4d6223204c15ac087a8c52973 has active endpoints

[CalvinNeo]

/run-all-tests

[CalvinNeo]

/run-all-tests

[CalvinNeo]

/run-unit-test