docs: fix invalid contributing-docs link (apache#48990)

Author: guan404ming

.github/workflows/news-fragment.yml

@@ -50,7 +50,7 @@ jobs:
           {
           printf "\033[1;33mMissing significant newsfragment for PR labeled with
           'airflow3.0:breaking'.\nCheck
-          https://github.com/apache/airflow/blob/main/contributing-docs/16_contribution_workflow.rst
+          https://github.com/apache/airflow/blob/main/contributing-docs/18_contribution_workflow.rst
           for guidance.\033[m\n"
           &&
           false

contributing-docs/03_contributors_quick_start.rst

@@ -747,7 +747,7 @@ Contribution guide
 
   .. |Workflow for a contribution| raw:: html
 
-   <a href="https://github.com/apache/airflow/blob/main/contributing-docs/16_contribution_workflow.rst" target="_blank">
+   <a href="https://github.com/apache/airflow/blob/main/contributing-docs/18_contribution_workflow.rst" target="_blank">
    Workflow for a contribution</a>
 
 

contributing-docs/README.rst

@@ -34,7 +34,7 @@ New Contributor
 If you are a new contributor, please follow the `Contributors Quick Start <03_contributors_quick_start.rst>`__
 guide for a step-by-step introduction to setting up the development environment and making your
 first contribution.
-We also suggest you to check out `Contribution Workflow <16_contribution_workflow.rst>`__ in order to get an overview of how to
+We also suggest you to check out `Contribution Workflow <18_contribution_workflow.rst>`__ in order to get an overview of how to
 contribute to Airflow.
 
 If you are new to the project, you might need some help in understanding how the dynamics

dev/MANUALLY_GENERATING_IMAGE_CACHE_AND_CONSTRAINTS.md

@@ -65,7 +65,7 @@ merges to `main` branch builds (also known as `canary` builds) have separate mai
 take care about refreshing the cache that is used to speed up our builds and to speed up
 rebuilding of [Breeze](./breeze/doc/README.rst) images for development purpose. This is all happening automatically, usually:
 
-* The latest [constraints](/contributing-docs/12_airflow_dependencies_and_extras.rst#pinned-constraint-files) are pushed to appropriate branch after all tests succeed in the
+* The latest [constraints](/contributing-docs/13_airflow_dependencies_and_extras.rst#pinned-constraint-files) are pushed to appropriate branch after all tests succeed in the
   `canary` build.
 
 * The [images](breeze/doc/ci/02_images.md) in `ghcr.io` registry are refreshed early at the beginning of the

dev/breeze/doc/09_release_management_tasks.rst

@@ -428,7 +428,7 @@ Whenever ``pyproject.toml`` gets modified, the CI main job will re-generate cons
 files are stored in separated orphan branches: ``constraints-main``, ``constraints-2-0``.
 
 Those are constraint files as described in detail in the
-`</contributing-docs/12_airflow_dependencies_and_extras.rst#pinned-constraint-files>`_ contributing documentation.
+`</contributing-docs/13_airflow_dependencies_and_extras.rst#pinned-constraint-files>`_ contributing documentation.
 
 
 You can use ``breeze release-management generate-constraints`` command to manually generate constraints for

providers-summary-docs/howto/create-custom-providers.rst

@@ -155,7 +155,7 @@ they define the extensions properly. See :doc:`apache-airflow:cli-and-env-variab
 sub-commands.
 
 When you write your own provider, consider following the
-`Naming conventions for providers <https://github.com/apache/airflow/blob/main/contributing-docs/11_provider_distributions.rst#naming-conventions-for-provider-distributions>`_
+`Naming conventions for providers <https://github.com/apache/airflow/blob/main/contributing-docs/12_provider_distributions.rst#naming-conventions-for-provider-distributions>`_
 
 Special considerations
 ''''''''''''''''''''''