Make the default log level warning

[jsf9k]

🗣 Description

Make the default log level warning. This will help prevent guacscanner logs from growing too large.

💭 Motivation and context

Resolves cisagov/guacamole-composition#54.

🧪 Testing

All automated tests pass.

✅ Pre-approval checklist

• This PR has an informative and human-readable title.
• Changes are limited to a single goal - eschew scope creep!
• All relevant type-of-change labels have been added.
• I have read the CONTRIBUTING document.
• These code changes follow cisagov code standards.
• All new and existing tests pass.

✅ Pre-merge checklist

• Finalize version.

✅ Post-merge checklist

• Create a release.

[coveralls]

Pull Request Test Coverage Report for Build 3362436755

• 1 of 1 (100.0%) changed or added relevant line in 1 file are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 76.965%

---

Totals
Change from base Build 3146577391:	0.0%
Covered Lines:	218
Relevant Lines:	265

---

💛 - Coveralls

[dav3r]

👍 👍 Less disk!! 💾

[mcdonnnj]

So I don't specifically have an issue with this, but do we want to instead change Docker behavior instead of limiting the logging information from this package? We could update cisagov/guacamole-composition to log to AWS CloudWatch or just adjust the retention rules for the default json-file driver. I'm not a big fan of adjusting Python package behavior because of a downstream implementation problem when possible. Just for completeness all information about Docker logging configuration can be found here.

[jsf9k]

Closed in favor of adjusting the retention settings for the json-file Docker logging driver in cisagov/guacamole-composition, as suggested by @mcdonnnj.

[jsf9k]

Please see cisagov/guacamole-composition#54 and cisagov/guacamole-composition#55.