Update bzlmod migration to mention enable_bzlmod

It the migration guide make sure to explicitly tell the user to update their `.bazelrc` with the `--enable_bzlmod` so that Bzlmod will be active.  This resolves #19561

Closes #19574.

PiperOrigin-RevId: 567355957
Change-Id: I162122a90e840e022ac3ed421b7006ee31d30aa3

site/en/external/migration.md

@@ -32,6 +32,19 @@ your workspace root, maybe with comments like:
     # See MODULE.bazel for external dependencies setup.
     ```
 
+### Enable Blzmod in your bazelrc {:#enable-bzldmod}
+
+`.bazelrc` lets you set flags that apply every time your run Bazel. To enable
+Bzlmod, use the `--enable_bzlmod` flag, and apply it to the `common` command so
+it applies to every command:
+
+* **.bazelrc**
+
+    ```
+    # Enable Bzlmod for every Bazel command
+    common --enable_bzlmod
+    ```
+
 ### Specify repository name for your workspace {:#specify-repo-name}
 
 *   **WORKSPACE**