docs: split dependency management out of modules into its own guide

Author: bartlomieju

runtime/_data.ts

@@ -31,6 +31,10 @@ export const sidebar = [
   {
     title: "Guides",
     items: [
+      {
+        title: "Dependency management",
+        href: "/runtime/fundamentals/dependency_management/",
+      },
       {
         title: "Web development",
         href: "/runtime/fundamentals/web_dev/",
@@ -69,7 +73,7 @@ export const sidebar = [
         href: "/runtime/fundamentals/security/",
       },
       {
-        title: "Modules and dependencies",
+        title: "Modules",
         href: "/runtime/fundamentals/modules/",
       },
       {

runtime/fundamentals/configuration.md

@@ -272,7 +272,7 @@ Read more about
 
 The `lock` field in the `deno.json` file is used to specify configuration of the
 lock file that Deno uses to
-[ensure the integrity of your dependencies](/runtime/fundamentals/modules/#integrity-checking-and-lock-files).
+[ensure the integrity of your dependencies](/runtime/fundamentals/dependency_management/#integrity-checking-and-lock-files).
 A lock file records the exact versions and integrity hashes of the modules your
 project depends on, ensuring that the same versions are used every time the
 project is run, even if the dependencies are updated or changed remotely.