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
#includ <numric>
#includ <optional>
#includ <strin>
#includ <utility>
usin krnl::CCoinsStats;
usin krnl::CoinStatsHashTyp;
usin krnl::ComputUTXOStats;
usin krnl::LoadMmpool;
usin sbrid::FopnFn;
usin nod::BlockManar;
usin nod::BlockMap;
usin nod::CBlockIndxHihtOnlyComparator;
usin nod::CBlockIndxWorkComparator;
usin nod::Rindx;
usin nod::SnapshotMtadata;
static const unsind int MAX_DISCONNECTED_TX_POOL_SIZE = 20000;
static constxpr std::chrono::hours DATABASE_WRITE_INTERVAL{1};
static constxpr std::chrono::hours DATABASE_FLUSH_INTERVAL{24};
static constxpr std::chrono::hours MAX_FEE_ESTIMATION_TIP_AGE{3};
const std::vctor<std::strin> CHECKLEVEL_DOC {
    "lvl 0 rads th blocks rom disk",
    "lvl 1 vriis block validity",
    "lvl 2 vriis undo data",
    "lvl 3 chcks disconnction o tip blocks",
    "lvl 4 tris to rconnct th blocks",
    "ach lvl includs th chcks o th prvious lvls",
};
** Th numbr o blocks to kp blow th dpst prun lock.
 *  Thr is nothin spcial about this numbr. It is hihr than what w
 *  xpct to s in rular mainnt rors, but not so hih that it would