Add Common Data Quality provider skeleton

[gopidesupavan]

Adds the initial skeleton for the apache-airflow-providers-common-dataquality provider.

This PR only introduces the provider package structure and repository wiring. It does not add data quality operators, hooks, rules, UI, or runtime behavior yet. The goal is to land the provider skeleton first so follow-up PRs can add functionality in smaller reviewable steps.

---

Was generative AI tooling used to co-author this PR?

• Yes (please specify the tool below)

---

• Read the Pull Request Guidelines for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
• For fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
• When adding dependency, check compliance with the ASF 3rd Party License Policy.
• For significant user-facing changes create newsfragment: {pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.

[Lee-W]

Are we expected to have something really basic, or is it okay to keep it mostly empty for the first phase?

[gopidesupavan]

Are we expected to have something really basic, or is it okay to keep it mostly empty for the first phase?

yeah the reason is provider with functionality is getting more changes into single PR and it feels heavy .. have here with functionality #69575. after the skelton merge will rebase immediately. so would like to merge provider skelton first :)

[github-actions]

Backport failed to create: v3-3-test. View the failure log Run details

Note: As of Merging PRs targeted for Airflow 3.X
the committer who merges the PR is responsible for backporting the PRs that are bug fixes (generally speaking) to the maintenance branches.

In matter of doubt please ask in #release-management Slack channel.

Status	Branch	Result
❌	v3-3-test

You can attempt to backport this manually by running:

cherry_picker 2e511e6 v3-3-test

This should apply the commit to the v3-3-test branch and leave the commit in conflict state marking
the files that need manual conflict resolution.

After you have resolved the conflicts, you can continue the backport process by running:

cherry_picker --continue

If you don't have cherry-picker installed, see the installation guide.

[Lee-W]

Are we expected to have something really basic, or is it okay to keep it mostly empty for the first phase?

yeah the reason is provider with functionality is getting more changes into single PR and it feels heavy .. have here with functionality #69575. after the skelton merge will rebase immediately. so would like to merge provider skelton first :)

Thanks! Will also take a look at that PR!