fix(ingest): resolve issue with caplog and asyncio

[hsheth2]

We're starting to see issues like this in CI, likely due to a dependency upgrade (probably freezegun https://pypi.org/project/freezegun/ - see discussion here spulec/freezegun#521)

When using caplog, we see a stray asyncio log message before the rest of the logs. This should clear that out.

FAILED tests/unit/api/source_helpers/test_source_helpers.py::test_auto_empty_dataset_usage_statistics - assert not [<LogRecord: asyncio, 10, /opt/hostedtoolcache/Python/3.7.17/x64/lib/python3.7/asyncio/selector_events.py, 58, "Using selector: %s">]
 +  where [<LogRecord: asyncio, 10, /opt/hostedtoolcache/Python/3.7.17/x64/lib/python3.7/asyncio/selector_events.py, 58, "Using selector: %s">] = <_pytest.logging.LogCaptureFixture object at 0x7f067d18d9d0>.records
FAILED tests/unit/api/source_helpers/test_source_helpers.py::test_auto_empty_dataset_usage_statistics_invalid_timestamp - assert 2 == 1
 +  where 2 = len([<LogRecord: asyncio, 10, /opt/hostedtoolcache/Python/3.7.17/x64/lib/python3.7/asyncio/selector_events.py, 58, "Using selector: %s">, <LogRecord: datahub.ingestion.api.source_helpers, 30, /home/runner/work/datahub/datahub/metadata-ingestion/src/datahub/ingestion/api/source_helpers.py, 358, "1970-01-01 00:00:00+00:00">])
 +    where [<LogRecord: asyncio, 10, /opt/hostedtoolcache/Python/3.7.17/x64/lib/python3.7/asyncio/selector_events.py, 58, "Using selector: %s">, <LogRecord: datahub.ingestion.api.source_helpers, 30, /home/runner/work/datahub/datahub/metadata-ingestion/src/datahub/ingestion/api/source_helpers.py, 358, "1970-01-01 00:00:00+00:00">] = <_pytest.logging.LogCaptureFixture object at 0x7f0689f161d0>.records

Example failure: https://github.com/datahub-project/datahub/actions/runs/7084142887/job/19277839780

Checklist

• The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
• Links to related issues (if applicable)
• Tests for the changes have been added/updated (if applicable)
• Docs related to the changes have been added/updated (if applicable). If a new feature has been added a Usage Guide has been added for the same.
• For any breaking change/potential downtime/deprecation/big changes an entry has been made in Updating DataHub

[asikowitz]

I made similar changes in one of my PRs. Think they're actually identical so hopefully no merge conflicts