fix: correct suggestion status (#299)

<!-- 👋 Hi, thanks for sending a PR to eslint-plugin-package-json! 💖.
Please fill out all fields below and make sure each item is true and [x]
checked.
Otherwise we may not be able to review your PR. -->

## PR Checklist

-   [x] Addresses an existing open issue: fixes #255
- [x] That issue was marked as [`status: accepting
prs`](https://github.com/JoshuaKGoldberg/eslint-plugin-package-json/issues?q=is%3Aopen+is%3Aissue+label%3A%22status%3A+accepting+prs%22)
- [x] Steps in
[CONTRIBUTING.md](https://github.com/JoshuaKGoldberg/eslint-plugin-package-json/blob/main/.github/CONTRIBUTING.md)
were taken

## Overview

<!-- Description of what is changed and how the code change does that.
-->

README.md

@@ -120,10 +120,10 @@ The default settings don't conflict, and Prettier plugins can quickly fix up ord
 | [sort-collections](docs/rules/sort-collections.md)                     | Dependencies, scripts, and configuration values must be declared in alphabetical order.         | ✅  | 🔧 |    |
 | [unique-dependencies](docs/rules/unique-dependencies.md)               | Enforce that if repository directory is specified, it matches the path to the package.json file | ✅  |    | 💡 |
 | [valid-local-dependency](docs/rules/valid-local-dependency.md)         | Checks existence of local dependencies in the package.json                                      | ✅  |    |    |
-| [valid-name](docs/rules/valid-name.md)                                 | Enforce that package names are valid npm package names                                          | ✅  |    | 💡 |
+| [valid-name](docs/rules/valid-name.md)                                 | Enforce that package names are valid npm package names                                          | ✅  |    |    |
 | [valid-package-def](docs/rules/valid-package-def.md)                   | Enforce that package.json has all properties required by the npm spec                           | ✅  |    |    |
 | [valid-repository-directory](docs/rules/valid-repository-directory.md) | Enforce that if repository directory is specified, it matches the path to the package.json file | ✅  |    | 💡 |
-| [valid-version](docs/rules/valid-version.md)                           | Enforce that package versions are valid semver specifiers                                       | ✅  |    | 💡 |
+| [valid-version](docs/rules/valid-version.md)                           | Enforce that package versions are valid semver specifiers                                       | ✅  |    |    |
 
 <!-- end auto-generated rules list -->
 <!-- prettier-ignore-end -->

docs/rules/valid-name.md

@@ -2,8 +2,6 @@
 
 💼 This rule is enabled in the ✅ `recommended` config.
 
-💡 This rule is manually fixable by [editor suggestions](https://eslint.org/docs/latest/use/core-concepts#rule-suggestions).
-
 <!-- end auto-generated rule header -->
 
 This rule applies two validations to the `"name"` property:

docs/rules/valid-version.md

@@ -2,8 +2,6 @@
 
 💼 This rule is enabled in the ✅ `recommended` config.
 
-💡 This rule is manually fixable by [editor suggestions](https://eslint.org/docs/latest/use/core-concepts#rule-suggestions).
-
 <!-- end auto-generated rule header -->
 
 This rule applies two validations to the `"name"` property:

src/rules/valid-name.ts

@@ -48,7 +48,6 @@ export const rule = createRule({
 				"Enforce that package names are valid npm package names",
 			recommended: true,
 		},
-		hasSuggestions: true,
 		messages: {
 			invalid: "Invalid npm package name: {{ complaints }}.",
 			type: '"name" should be a string.',

src/rules/valid-version.ts

@@ -39,7 +39,6 @@ export const rule = createRule({
 				"Enforce that package versions are valid semver specifiers",
 			recommended: true,
 		},
-		hasSuggestions: true,
 		messages: {
 			invalid: "Version is not a valid semver specifier.",
 			type: '"version" should be a string.',