Prototype profile data analyzer

[yungyuc]

Profiling is a requirement before any HPC code can be written. A good profiling sub-system makes it easy to collaborate on performance improvement and tuning. External profiling tools may assist with additional details, but are less productive in the collaboration.

Attempts to improve the experimental profiler have been started (see #302). As mentioned in the issue, 3 key points are identified:

1. Integration of the profile data in both Python and C++. That is, the sub-system is implemented in C++, but wrapped to Python to support also profiling Python constructs. There will be 2 derivations:
   1. Integrate the C++ and Python call stacks in the modmesh profiler.
   2. Connect the modmesh profiler to the Python profiling sub-system (cProfile).
2. Serialize (and deserialize) the profile data.
3. Visualizing the profile results (data) from memory. Profile data can be persisted to storage through the serialization and deserialized for visualization.

This topic thread is created to collect development information and track the progress.

---

Plan for 20240518 scisprint

In the May scisprint we will clarify PR #315 (wrapper) and #323 (serializer) and move them forward. We will discuss the challenges and set a milestone for the wrapper and serializer.

[yungyuc]

Wrapper of the profiler data objects has been started with PR #315 by @q40603 .

[yungyuc]

A prototype of the serializer has been started with PR #323 by @ThreeMonth03 .