Reduced the volume of logging from the botocore library

[Kyle-Neale]

What does this PR do?

This prevents propagation of botocore logs into the Agent.

Motivation

yyyy-MM-dd HH:mm:ss UTC | CORE | INFO | (pkg/collector/python/* in LogMessage) | - | (credentials.py:1075) | Found credentials from IAM Role: *

This log pattern spams the Agent every time the check is run so we prevent this from happening by setting the botocore
log level to CRITICAL

Review checklist (to be filled by reviewers)

• Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
• Add the qa/skip-qa label if the PR doesn't need to be tested during QA.
• If you need to backport this PR to another branch, you can add the backport/<branch-name> label to the PR and it will automatically open a backport PR once this one is merged

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 88.56%. Comparing base (edf5718) to head (89b3d3e).
Report is 12 commits behind head on master.

Additional details and impacted files

Flag	Coverage Δ
activemq	?
amazon_msk	89.24% <100.00%> (+0.04%)	⬆️
cassandra	?
hive	?
hivemq	?
hudi	?
ignite	?
jboss_wildfly	?
kafka	?
presto	?
solr	?

Flags with carried forward coverage won't be shown. Click here to find out more.

[nubtron]

Thanks @Kyle-Neale! And @dkirov-dd for finding setLevel!

[nubtron]

@Kyle-Neale A changelog entry could be useful here, so that the Agent team can track the fix, and in case customers have noticed it.

[nubtron]

Just a comment! We still log at the critical level, so we're not totally preventing the logging. Also the people reading the log will be waiting for something like "Reduced the volume of logging from the botocore library".