✨ [source-klaviyo] Use latest CDK and continue syncing even if a stream fails

[brianjlai]

Temporarily includes the test code to validate the fix works with the latest CDK. The bad code will be removed before merging

Closes #29882

What

Modifies the klaviyo source to uptake the latest CDK changes which allows the source to continue a sync even when one of the streams exits due to a failure during the sync

How

Overrides the new continue_sync_on_stream_failure() method which will cause it to keep syncing which was introduced in 0.56.0 #33136

Again I will highlight that this will impact our ability to group Sentry errors together so we should be conservative where we apply this fix while we work on the proper interface.

[vercel]

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

Name	Status	Preview	Comments	Updated (UTC)
airbyte-docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Dec 8, 2023 0:04am

[github-actions]

Before Merging a Connector Pull Request

Wow! What a great pull request you have here! 🎉

To merge this PR, ensure the following has been done/considered for each connector added or updated:

• PR name follows PR naming conventions
• Breaking changes are considered. If a Breaking Change is being introduced, ensure an Airbyte engineer has created a Breaking Change Plan.
• Connector version has been incremented in the Dockerfile and metadata.yaml according to our Semantic Versioning for Connectors guidelines
• You've updated the connector's metadata.yaml file any other relevant changes, including a breakingChanges entry for major version bumps. See metadata.yaml docs
• Secrets in the connector's spec are annotated with airbyte_secret
• All documentation files are up to date. (README.md, bootstrap.md, docs.md, etc...)
• Changelog updated in docs/integrations/<source or destination>/<name>.md with an entry for the new version. See changelog example
• Migration guide updated in docs/integrations/<source or destination>/<name>-migrations.md with an entry for the new version, if the version is a breaking change. See migration guide example
• If set, you've ensured the icon is present in the platform-internal repo. (Docs)

If the checklist is complete, but the CI check is failing,

1. Check for hidden checklists in your PR description

2. Toggle the github label checklist-action-run on/off to re-run the checklist CI.

[girarda]

🚢