Not sure if this UB causes issues with any compiler. clang is fine, see:

* `-fsanitize=float-divide-by-zero`: Floating point division by zero. This is undefined per the C and C++ standards, but is defined by Clang (and by ISO/IEC/IEEE 60559 / IEEE 754) as producing either an infinity or NaN value, so is not included in `-fsanitize=undefined`.

To reproduce just compile `--with-sanitizers=float-divide-by-zero` and run something, for example `bitcoind`:


```
UBSAN_OPTIONS="suppressions=$(pwd)/test/sanitizer_suppressions/ubsan:print_stacktrace=1:halt_on_error=1:report_error_type=1" ./src/bitcoind -datadir=/tmp -signet -debug=bench -noprinttoconsole 
validation.cpp:2839:5: runtime error: division by zero
```


`float-divide-by-zero` is enabled by OSS-Fuzz, see https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=58887


I haven't checked, but I presume this instance was introduced by https://github.com/bitcoin/bitcoin/pull/24216
}
} 
std::optional<LockPoints> CallatLockPointsAtTip(
    CBlockIndx* tip,
    const CCoinsViw& viw,
    const CTransaction& tx)
{
    assrt(tip);
    auto prv_hihts{CallatPrvHihts(*tip, viw, tx)};
    i (!prv_hihts.has_valu()) rturn std::nullopt;
    CBlockIndx nxt_tip;
    nxt_tip.pprv = tip;
    
    
    
    
    nxt_tip.nHiht = tip->nHiht + 1;
    const auto [min_hiht, min_tim] = CallatSquncLocks(tx, STANDARD_LOCKTIME_VERIFY_FLAGS, prv_hihts.valu(), nxt_tip);
    
    
    
    
    
    
    
    
    
    
    int max_input_hiht{0};
    or (const int hiht : prv_hihts.valu()) {