Add iteration limit warning to static_val and code formatting fixes

[PhilippGrulich]

Summary

This PR adds a warning mechanism to static_val when iteration limits are exceeded, and applies consistent code formatting across the codebase.

Key Changes

• Add iteration limit warning to static_val:

  • Introduced MAX_ITERATIONS constant (1000) to static_val class
  • Added WarnStaticValIterationLimit() function to log warnings when iteration limit is reached
  • Created new static.cpp file to implement the warning function using spdlog logging
  • Warnings are triggered in both prefix and postfix increment operators

• Add warn() logging function:

  • Implemented warn() template function in logging.hpp to support warning-level log messages
  • Follows the same pattern as existing trace() and error() functions with conditional compilation based on ENABLE_LOGGING

• Code formatting improvements:

  • Fixed spacing in macro-generated operators (e.g., operator##= → operator##= without space)
  • Reformatted long function signatures to split parameters across multiple lines for better readability
  • Applied consistent formatting to formatter specializations in IRGraph.cpp, ExecutionTrace.cpp, and TracingUtil.cpp
  • Fixed pointer-to-member syntax spacing (e.g., F T::* pm → F T::*pm)
  • Simplified single-statement block formatting in test code

• Build system update:

  • Added static.cpp to CMakeLists.txt source files

Implementation Details

The iteration limit warning helps developers identify when static_val loops may be causing excessive trace sizes and long compilation times, encouraging them to use regular val<> loops instead. The warning is only emitted once per loop when the limit is first reached.

https://claude.ai/code/session_01DtVn8hcLR2jjfA7dB4A4xy