AMReX Tiny Profiler Context

[ax3l]

As users start to extend routines on the Python side - and we add more wrappers on bindings - we should start profiling these sections to catch unexpected bottlenecks.
For that, we should wrap and expose the BL_PROFILE logic.

BL_PROFILE are lightweight macros that wrap C++ object that start/stop profiling. We might want to wrap the underling C++ objects directly first. Then, we might add some convenience helper functions/objects as well, if needed.

[ax3l]

This could be implemented similar to cupy's profiler with an __enter__/__exit__ that can be used within a with: context manager (and thus does not rely on destructor calls for the time measurement).

Example:

• https://github.com/AMReX-Codes/pyamrex/blob/ae39119ca49dabd3023bcc9d45dd74a8428609bf/tests/test_multifab.py#LL210C5-L211C1
• creates: Array4: __cuda_array_interface__ v3 #30 (comment)