CLN/PERF: remove catching of numpy deprecation warning in comparison_op

[jorisvandenbossche]

xref #39146

In some of the FrameWithFrameWide benchmarks, this takes up around 15% of the time.

While I don't think this should be needed (but let's see if warnings appear in the CI builds).

[jorisvandenbossche]

@jbrockmendel this warning filter was added in #32779. AFAIU, the reason the warning turned up in that PR is because you started to perform ops blockwise (using a 2D numpy datetime64[ns] array), instead going through Series op (where we use the EA).

arithmetic_op already calls ensure_wrapped_if_datetimelike on both left/right operands, so this makes comparison_op consistent with that (I know I would like to move out ensure_wrapped_if_datetimelike alltogether, but can be dealt with together with the other occurences later).

[jbrockmendel]

This looks like a good trade to me!