feat(cdk): port QA checks from airbyte-ci to airbyte-python-cdk

[devin-ai-integration]

Description

This PR ports the quality assurance (QA) checks from airbyte-ci to the airbyte-python-cdk, creating a new module at airbyte_cdk.qa with a CLI command airbyte-cdk connector pre-release-check.

Changes

• Created a new module airbyte_cdk.qa with the following components:
  • Core abstractions in models.py for Check, CheckResult, and Report classes
  • Simplified Connector class in connector.py with minimal dependencies
  • Ported checks for assets, documentation, metadata, packaging, security, and testing
  • Added CLI implementation for running pre-release checks
• Added comprehensive docstrings to the module describing the checks, configuration options, and usage
• Added dependencies for semver and pydash to support the QA checks
• Added unit tests for the Connector and CheckResult classes

How to test

Run the CLI command:

airbyte-cdk connector pre-release-check --connector-name <connector-name>

Requested by

Aaron ("AJ") Steers (aj@airbyte.io)

Link to Devin run

https://app.devin.ai/sessions/765c11efdefa43578eb78b1308e7b89a

[devin-ai-integration]

Original prompt from Aaron:

@Devin - Can you help me create a plan to refactor or port the "quality assurance" or "qa" checks for connectors, from airbyte-ci into either the airbyte python cdk, or else into a standalone app or script? Can you tell me how portable the code is as of now, and which specific code files contain the logic? Also let me know if it relies on dagger/docker at all

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment and CI monitoring

[Aaron ("AJ") Steers (aaronsteers)]

do we need all these?

[devin-ai-integration]

The markers are used to filter tests based on connector properties. We can simplify this by keeping only the essential ones:

Essential markers:

• qa_check: Identifies tests that are QA checks
• check_category: Categorizes checks (metadata, security, etc.)
• requires_metadata: Indicates if a check needs metadata.yaml
• connector_language: Filters by connector language (Python, Java, etc.)

Optional markers that could be removed:

• connector_type, connector_support_level, connector_cloud_usage: These are more granular filters
• connector_ab_internal_sl: Very specific to internal support levels
• runs_on_released_connectors: Could be simplified

I can reduce these to just the essential markers if preferred.

[devin-ai-integration]

Closing due to inactivity for more than 7 days.