I don't see how java tooling is any more complex than any other language, they all have learning curves. Even Python has complexities around venv, requirements, pipfile etc. C's tooling in particular is probably the worst. You have to learn the compiler, the linker, or a 3rd party tool like cmake or meson.
Using an IDE in Java is a choice just like picking PyCharm is for python.
I agree with you in general, but here I am discussing introductory CS programs. It's very hard for an intro CS student to build and run a Java program without an IDE, even with help from the professor. It's completely trivial for that same student to write and run most of the Python programs they'll be doing in their intro class after having installed _just Python_.
I feel like this kind of makes the point though... while all of this tooling does exist for Python, it's very easy to use Python without any of it at all. So it can be relegated to more of an advanced, 'production-ready' topic, e.g. in a software engineering course. Indeed, I've never seen an intro course in either Python or C that touches on any of this tooling, save one professor who distributed a standard makefile for his intro C course - but I'm honestly not sure why. It usually suffices just fine to have the students call gcc themselves, the projects they work on in the first year aren't big enough to make this cumbersome.
While that's partially true of Java, it's less true of Java. More of the tooling around Java is de facto required.
Using an IDE in Java is a choice just like picking PyCharm is for python.