Remove the abandoned logging framework log4j 1.x

**Is your feature request related to a problem? Please describe.**
Yes, a lot of trouble configuring logging for new applications.
Right now this project uses the log4j 1.x and its accompanying slf4j binding library.
In any new project with the Apache Beam framework, we have to try and find a way to bind the slf4j to another logging framework because the log4j 1.x is abandoned and has very few features. There is also the problem of binding the slf4j to another framework resulting in double binding.

**Describe the solution you'd like**
Remove the binding to the abandoned log4j 1.x library

**Describe alternatives you've considered**
Tried binding the slf4j to another logging framework.

**Additional context**
The log4j 1.x comes as result of the transitive dependencies of the project and if removed gives other errors on the bigtable-hbase logging. Just to find the project that transitively imports this library is a pain!!!

Es werden keine Dateien oder Tests genannt. Beginne damit, den Abhängigkeitsgraphen des Projekts zu untersuchen, um herauszufinden, welche transitive Abhängigkeit log4j 1.x und dessen slf4j-Binding einbindet, und untersuche anschließend die gemeldeten bigtable-hbase-Logging-Fehler. Als abgeschlossen gilt die Aufgabe, wenn das aufgegebene Binding entfernt wurde, ohne Logging- oder Double-Binding-Fehler einzuführen.

Vom Indexierungsmodell aus dem Issue-Text verfasst.