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!!!

Non vengono indicati file o test. Inizia ispezionando il grafo delle dipendenze del progetto per individuare quale dipendenza transitiva introduce log4j 1.x e il relativo binding slf4j, quindi analizza gli errori di logging segnalati di bigtable-hbase. Il lavoro è completato quando il binding abbandonato viene rimosso senza introdurre errori di logging o di double-binding.

Scritto dal modello di indicizzazione a partire dal testo della issue.