Change default logging level, document Logback config

[Luke-Sikina]

Fix #9538. Describe changes proposed in this pull request:

• Use the provided logback EXAMPLE file by default. This changes the current default of DEBUG logging everything which caused performance issues in portals with authentication. This was introduced in v4.0.2.
• update poms with new excludes
• update main pom to copy logback config
• update README with logback info

[sheridancbio]

I'm approving, although we should not rely on me alone. My understanding now is that a switch in logging was made months ago to logback configuration, but the configuration files in the build setup (pom.xml) fell out of sync. This PR seems to give updated guidance to deployers on how to configure logback (dropping guidance on log4j config files), and has the logic for including the logback.xml-EXAMPLE file in the build when the user does not provide a custom logback.xml file of their own.

The fact that the pom.xml reference to logback.xml is in an <exclude> element is a little confusing to me --- because I think we want them included during build. But maybe this is to exclude them from getting bundled into sub-modules as they are deployed at the root level.

👍

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

[inodb]

Changed the title and description slightly b/c I think the critical piece is that this changes the default Docker setup to no longer do debug logging by default. Feel free to change tho