Switch recommended to errors, and from recommended-error to recommended-warn?

[JoshuaKGoldberg]

Motivation

To my knowledge, eslint-plugin-jsdoc's recommended and recommended-typescript preset configs are the only popular ones in the ESLint community whose default severities are set to "warn" instead of "error". That means this is the only plugin whose config extends values mention severity.

(I haven't used other shared configs from this plugin, but the same thoughts apply to them)

For example, in create-typescript-app, .ts files receive the equivalent of:

extends: [
	"eslint:recommended",
	"plugin:eslint-comments/recommended",
	"plugin:n/recommended",
	"plugin:perfectionist/recommended-natural",
	"plugin:regexp/recommended",
	"plugin:vitest/recommended",
	"plugin:jsdoc/recommended-typescript-error",
	"plugin:@typescript-eslint/strict-type-checked",
	"plugin:@typescript-eslint/stylistic-type-checked",
]

Current behavior

• plugin:jsdoc/recommended and plugin:jsdoc/recommended-typescript set rules to "warn" severity
• plugin:jsdoc/recommended-error and plugin:jsdoc/recommended-typescript-error set rules to "error" severity

Desired behavior

As a breaking change in a new major version:

• Switch plugin:jsdoc/recommended and plugin:jsdoc/recommended-typescript to "error" severity
• Mark plugin:jsdoc/recommended-error and plugin:jsdoc/recommended-typescript-error as @deprecated
• Create new plugin:jsdoc/recommended-warn and plugin:jsdoc/recommended-typescript-warn configs that set rules to "warn" severity

Alternatives considered

Keep things as they are, I suppose?

[brettz9]

Any thoughts, @gajus ? Parity might be nice, but eslint-plugin-jsdoc may be different from other plugins in not being critical enough to the average project to have as errors.