docs: explicitly specify that the migrate command writes individual linters of the presets to the linters.enable field

Author: kyu08

docs/src/docs/product/migration-guide.mdx

@@ -37,6 +37,8 @@ The `migrate` command enforces the following default values:
 - `run.concurrency`: if the existing value was `0`, it is removed as `0` is the new default.
 - `run.relative-path-mode`: if the existing value was `cfg`, it is removed as `cfg` is the new default.
 
+`linters.presets` has been removed. The `migrate` command **automatically adds individual linters to `linters.enable`.**
+
 `issues.exclude-generated` has a new default value (v1 `lax`, v2 `strict`), so this field will be added during the migration to maintain the previous behavior.
 
 `issues.exclude-dirs-use-default` has been removed, so it is converted to `linters.exclusions.paths` and, if needed, `formatters.exclusions.paths`.
@@ -189,7 +191,7 @@ There are 2 new options (they are not strictly equivalent to the previous option
 
 #### `linters.presets`
 
-This property have been removed.
+This property has been removed. The `migrate` command **automatically adds individual linters to `linters.enable`.**
 
 <details>
 <summary style={{color: '#737380', paddingLeft: '1rem'}}>v1</summary>