chore: replace AirbyteLogger with logging.Logger in connectors

[natikgadzhi]

What

This commit does all the AirbyteLogger replacing in a single pass, without bumping connector versions. Here's why I did this (internal Slack).

The goal here is to take all connectors to be more ready to update, without spending a week on extra hoops. This change seems very safe and tactical.

This closes https://github.com/airbytehq/airbyte-internal-issues/issues/8406.

How

Replaces:

• from airbyte_cdk import AirbyteLogger -> import logging
• from airbyte_cdk.logger import AirbyteLogger -> import logging
• logger: AirbyteLogger -> logger: logging.Logger
• AirbyteLogger() -> logging.getLogger("airbyte")

And then airbyte-ci format fix all.

User Impact

None, connectors will not get republished.

Can this PR be safely reverted and rolled back?

• YES 💚
• NO ❌

Caveats

The CI on this will be very red because I'm changing connector code without bumping the version, so needs manual blessing from @alafanechere, @ChristoGrab, and @girarda.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Ignored Deployment

Name	Status	Preview	Comments	Updated (UTC)
airbyte-docs	⬜️ Ignored (Inspect)	Visit Preview		Jun 27, 2024 6:32am

[btkcodedev]

Hi, @alafanechere, Can you please review this PR
CC: @natikgadzhi

[natikgadzhi]

@btkcodedev well, shit. Our tooling is so cool that there are already too many pull requests that are conflicting with this.

We will have to open a new PR with these changes, bot on top of the fresh master.

@alafanechere before we do so, let's confirm that this PR is OK in spirit. What @btkcodedev will do is:

1. Replacing:
   from airbyte_cdk import AirbyteLogger -> import logging
   from airbyte_cdk.logger import AirbyteLogger -> import logging
   logger: AirbyteLogger -> logger: logging.Logger
   AirbyteLogger() -> logging.getLogger("airbyte")
2. airbyte-ci connectors --modified bump-version --patch -m "Refactor deprecated loggers"
3. airbyte-ci format fix all
4. Push a single large PR

At that point, it's a good idea to merge asap so we don't rack up new conflicts.

[alafanechere]

I'd 👍 this PR if it passed CI.
Multiple connectors are failing.
source-bing-ads for instance is failing it's unit tests for reasons which look related to logging.

My suggestion is to:

• Remove from this branch all connectors not passing CI
• Then we can safely merge this one once CI is 🟢 (@btkcodedev you can add the auto-merge label to the PR once you've made this change)
• Open per connector PR for the 🔴 one
• Manually inspect the failure reason of these 🔴 ones and use /approve-and-merge if they're definitely not related to the logger change.

Tooling wise the following flow can be followed to open per connectors PRs:

1. Make batch logger changes on all remaining connectors
2. Run airbyte-ci connectors --modified bump-version patch "replace AirbyteLogger..."
3. Run airbyte-ci connectors --modified pull-request --message="Replace AirbyteLogger...

[btkcodedev]

CI green for this branch

[btkcodedev]

Linking PRs with failed CI:
#40578
#40579
#40580
#40581
#40582
#40584
#40585
#40586
#40587
#40588
#40589