- sklearn changed location of private _print_elapsed_time
function in sklearn 1.5, which is breaking our code.
- To stay consistent but robust against such changes we
adapted the print functions and implement them ourselves.
This stops future code breaks due to location changes
and we stick to a similar logging style as sklearn.
- If sklearn is doing major changes to their logging style
we might should adapt in the future. However, that's
rather unlikely.