Improve log configuration when using multiple logging frameworks in Pipeline

We need to improve / document how to configure the different logging frameworks to support the different Beam modules (SDK/Runners/IOs).

I have seen this reported already in slack, but it also bit me recently when trying to log things with a module whose dependencies only supported java based logging over slf4j (no log4j). I tried to provide the classical log4j.properties but I could not get it to log anything, nothing from the sdk, and logically nothing from the java logging framework.

[Discussion on dev list](https://lists.apache.org/thread.html/502fc4a0575534ddd5f6abffd0743de8d2ccc7fee078b5922c2e1300@%3Cdev.beam.apache.org%3E)

Imported from Jira [BEAM-1757](https://issues.apache.org/jira/browse/BEAM-1757). Original Jira may contain additional context.
Reported by: iemejia.

Start with the linked dev-list discussion and review how logging is configured across the Beam SDK, runners, and IO modules. Document the supported configurations for the different logging frameworks, including the Java logging case described in the issue; done means users can determine how to obtain logs from the relevant modules.

Written by the indexing model from the issue text.