[TIR] Fixup max/min with input containing NAN

[actinks]

llvm.minimum and llvm.maximum: Return NaN if one the arguments is NaN.
refs: https://llvm.org/docs/LangRef.html#floating-point-min-max-intrinsics-comparison

fixed #19579

[gemini-code-assist]

Code Review

This pull request updates the LLVM code generation for minimum and maximum operations to use LLVM's CreateMinimum and CreateMaximum instructions for non-integer types. Feedback highlights that these instructions require LLVM 12 or later, so version guards are necessary to prevent compilation failures on older supported versions. It is also suggested to restrict these calls specifically to floating-point types for better type safety.

[actinks]

@tqchen The failing test case in ir_module.py is due to the LLVM backend lagging behind LLVM IR in its support for llvm.{min,max}imum.{f32,f64}. How should we handle this situation?
Related issue: llvm/llvm-project#53353

LLVM ERROR: Cannot select: 0x5d50add04bf0: f32 = fmaximum 0x5d50add04d28, ConstantFP:f32<0.000000e+00>, IRModule.CodeGenLLVM:0

The fmaximum instruction is supported in llvm 18.1.0 for x86-64 and in llvm 19.1.0 for i686.
proof:
X86-64: https://godbolt.org/z/b95xvbKxn
i686: https://godbolt.org/z/q39dr1bs9