docs: link to canonical plugin BOM documentation

Author: ayushHardeniya

content/doc/developer/testing/index.adoc

@@ -79,27 +79,10 @@ The following list covers typical integration tests:
 </dependency>
 ----
 
-To avoid manually managing dependency versions and to prevent conflicts between Jenkins components,
-it is recommended to use the Jenkins Bill of Materials (BOM).
-The BOM aligns compatible versions across the Jenkins ecosystem and is the standard approach
-for Jenkins plugin development.
+To avoid manually managing dependency versions and to prevent conflicts between Jenkins components, it is recommended to use the Jenkins Bill of Materials (BOM).
+The BOM aligns compatible versions across the Jenkins ecosystem and is the standard approach for Jenkins plugin development.
 
-[source,xml]
-----
-<dependencyManagement>
-  <dependencies>
-    <dependency>
-      <groupId>io.jenkins.tools.bom</groupId>
-      <artifactId>bom-${jenkins.version}.x</artifactId>
-      <version>${bom.version}</version>
-      <type>pom</type>
-      <scope>import</scope>
-    </dependency>
-  </dependencies>
-</dependencyManagement>
-----
-
-The BOM version should be selected to match the Jenkins version being tested to ensure dependency compatibility.
+Details on configuring and using the Jenkins plugin BOM are documented in the link:/doc/developer/tutorial-improve/use-plugin-bill-of-materials/[Use the plugin BOM] section of the Improve a plugin tutorial.
 
 ==== Depending on Other Plugins
 Any Jenkins plugins that you add as dependencies to your POM with `<scope>test</scope>` will be available in the Jenkins installations created while running test cases, or when using link:/doc/developer/tutorial/run/[`mvn hpi:run`].