Expose mimalloc metrics in Micrometer implementation

Description

Integrate mimalloc memory allocator metrics into the existing Micrometer metrics implementation to provide detailed memory allocation insights.

Background

mimalloc is a high-performance memory allocator that provides detailed metrics about memory allocation patterns, fragmentation, and performance. Exposing these metrics through our Micrometer implementation would provide valuable insights for memory optimization and leak detection.

Requirements

1. mimalloc Integration: Detect when mimalloc is being used as the memory allocator
2. Metric Exposure: Expose key mimalloc metrics through Micrometer
3. Performance Consideration: Ensure minimal overhead when collecting metrics
4. Documentation: Provide configuration and usage documentation

Acceptance Criteria

• Detect mimalloc availability and usage at runtime
• Expose core mimalloc metrics (heap usage, fragmentation, allocation stats)
• Integrate with existing Micrometer metric collection
• Add configuration options for metric collection frequency
• Maintain compatibility with other memory allocators (graceful fallback)
• Include metric labels for easy filtering and analysis
• Add comprehensive documentation for setup and usage

Technical Considerations

• Native integration with mimalloc statistics API
• JNI bindings or native library integration
• Conditional compilation/loading based on mimalloc availability
• Integration with containerized environments

Acceptance Criteria

• [Define what needs to be accomplished]

Additional Notes

[Any additional context or notes]

Start by locating the existing Micrometer metrics implementation and reviewing how it collects metrics. Then investigate mimalloc's statistics API and the proposed JNI or native-library loading approach, including allocator fallback behavior. Done means defining the metrics, configuration, labels, compatibility behavior, and documentation; the issue does not name specific files or tests.