Update qa-checks.md generation path to reflect Docusaurus multi-instance structure (#69181)

Co-authored-by: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
Co-authored-by: [email protected] <[email protected]>

Author: devin-ai-integration[bot]

airbyte-ci/connectors/connectors_qa/README.md

@@ -85,7 +85,7 @@ commit it in your PR.**:
 
 ```bash
 # From airbyte repo root
-connectors-qa generate-documentation docs/contributing-to-airbyte/resources/qa-checks.md
+connectors-qa generate-documentation docs/community/contributing-to-airbyte/resources/qa-checks.md
 ```
 
 ### Running tests

airbyte-ci/connectors/connectors_qa/src/connectors_qa/checks/documentation/templates/documentation_headers_check_description.md.j2

@@ -1,4 +1,4 @@
-The user facing connector documentation should follow the guidelines defined in the [standard template](../../../airbyte-ci/connectors/connectors_qa/src/connectors_qa/checks/documentation/templates/template.md.j2).
+The user facing connector documentation should follow the guidelines defined in the [standard template](https://github.com/airbytehq/airbyte/blob/master/airbyte-ci/connectors/connectors_qa/src/connectors_qa/checks/documentation/templates/template.md.j2).
 
 This check expects the following order of headers in the documentation:
 

airbyte-ci/connectors/connectors_qa/src/connectors_qa/checks/documentation/templates/section_content_description.md.j2

@@ -1,7 +1,7 @@
-The user facing connector documentation should follow the guidelines defined in the [standard template](../../../airbyte-ci/connectors/connectors_qa/src/connectors_qa/checks/documentation/templates/template.md.j2).
+The user facing connector documentation should follow the guidelines defined in the [standard template](https://github.com/airbytehq/airbyte/blob/master/airbyte-ci/connectors/connectors_qa/src/connectors_qa/checks/documentation/templates/template.md.j2).
 
 Check verifies that {{ header }} header section content follows standard template:
 
 ````
 {{ template }}
-````
+````

airbyte-ci/connectors/connectors_qa/src/connectors_qa/templates/qa_checks.md.j2

@@ -3,7 +3,7 @@
 <!--
 THIS FILE IS GENERATED BY THE CONNECTORS-QA CLI. DO NOT EDIT THIS FILE MANUALLY. 
 IF YOU NEED TO EDIT IT, EDIT THE TEMPLATE: https://github.com/airbytehq/airbyte/blob/master/airbyte-ci/connectors/connectors_qa/src/connectors_qa/templates/qa_checks.md.j2
-AND REGENERATE THE DOCS BY RUNNING `poetry run connectors-qa generate-documentation docs/connectors-qa.md`
+AND REGENERATE THE DOCS BY RUNNING `connectors-qa generate-documentation docs/community/contributing-to-airbyte/resources/qa-checks.md` FROM THE AIRBYTE REPO ROOT
 -->
 
 This document is listing all the static-analysis checks that are performed on the Airbyte connectors.

airbyte-ci/connectors/connectors_qa/tests/integration_tests/test_documentation.py

@@ -9,7 +9,7 @@
 
 from connectors_qa.cli import generate_documentation
 
-DOCUMENTATION_FILE_PATH_IN_AIRBYTE_REPO = Path("docs/contributing-to-airbyte/resources/qa-checks.md")
+DOCUMENTATION_FILE_PATH_IN_AIRBYTE_REPO = Path("docs/community/contributing-to-airbyte/resources/qa-checks.md")
 
 
 @pytest.fixture

docs/community/contributing-to-airbyte/resources/qa-checks.md

@@ -3,7 +3,7 @@
 <!--
 THIS FILE IS GENERATED BY THE CONNECTORS-QA CLI. DO NOT EDIT THIS FILE MANUALLY. 
 IF YOU NEED TO EDIT IT, EDIT THE TEMPLATE: https://github.com/airbytehq/airbyte/blob/master/airbyte-ci/connectors/connectors_qa/src/connectors_qa/templates/qa_checks.md.j2
-AND REGENERATE THE DOCS BY RUNNING `poetry run connectors-qa generate-documentation docs/connectors-qa.md`
+AND REGENERATE THE DOCS BY RUNNING `connectors-qa generate-documentation docs/community/contributing-to-airbyte/resources/qa-checks.md` FROM THE AIRBYTE REPO ROOT
 -->
 
 This document is listing all the static-analysis checks that are performed on the Airbyte connectors.
@@ -334,7 +334,7 @@ _Applies to connector with any support level_
 _Applies to connector with any internal support level_
 _Applies to connector with any Airbyte usage level_
 
-Connectors must be licensed under the MIT or Elv2 license. This is to ensure that all connectors are licensed under a permissive license. More details in our [License FAQ](https://docs.airbyte.com/community/licenses/license-faq).
+Connectors must be licensed under the MIT or Elv2 license. This is to ensure that all connectors are licensed under a permissive license. More details in our [License FAQ](https://docs.airbyte.com/developer-guides/licenses/license-faq).
 
 ### Connector license in metadata.yaml and pyproject.toml file must match
 
@@ -421,14 +421,14 @@ _Applies to connector with any Airbyte usage level_
 Connectors must use our Python connector base image (`docker.io/airbyte/python-connector-base`), declared through the `connectorBuildOptions.baseImage` in their `metadata.yaml`.
 This is to ensure that all connectors use a base image which is maintained and has security updates.
 
-## 🧪 Testing
+## 🔢 Version
 
-### Medium to High Use Connectors must enable acceptance tests
+### Connector Version Increment Check
 
-_Applies to the following connector types: source_
+_Applies to the following connector types: source, destination_
 _Applies to the following connector languages: java, low-code, python, manifest-only_
 _Applies to connector with any support level_
 _Applies to connector with any internal support level_
-_Applies to connector with medium, high Airbyte usage level_
+_Applies to connector with any Airbyte usage level_
 
-Medium to High Use Connectors must enable acceptance tests via the `connectorTestSuitesOptions.suite:acceptanceTests` in their respective metadata.yaml file to ensure that the connector is working as expected.
+Validates that the connector version was incremented if files were modified.