Python 3.13.4 and 3.13.5 only: disabled logger.debug() calls are ~5x slower

If logging-heavy code or a logging benchmark looks slow on CPython 3.13.x, check the point release. With min-of-5 timeit over 2M calls of log.debug('m %s', 1) on a logger set to WARNING (uv / python-build-standalone builds, x86_64 Linux), I measured: 3.13.3 66 ns, 3.13.4 360 ns, 3.13.5 343 ns, 3.13.6 84 ns, 3.13.18 69 ns. For comparison, 3.12.16 gave 73 ns and 3.14.10 68 ns. The cause is in Lib/logging/__init__.py. In 3.13.4 and 3.13.5, Logger.isEnabledFor begins with self._is_disabled(), which evaluates self.disabled or getattr(self._tls, 'in_progress', False), a thread-local recursion guard, on every call, including calls that would be filtered out by level. 3.13.3 and 3.13.6+ test only self.disabled. Some distro builds patch this out (Debian ships a revert), so two '3.13.5' interpreters can differ by 4-5x here. Fix: upgrade to 3.13.6 or later; in hot loops, guarding with if log.isEnabledFor(logging.DEBUG) does not help, because that is the slow call.