Bump eslint-plugin-jsdoc (#4922)

Author: DMarinhoCodacy

.github/instructions/codacy.instructions.md

@@ -6,13 +6,6 @@
 # Codacy Rules
 Configuration for AI behavior when interacting with Codacy's MCP Server
 
-## using any tool that accepts the arguments: `provider`, `organization`, or `repository`
-- ALWAYS use:
- - provider: gh
- - organization: codacy
- - repository: codacy-eslint
-- Avoid calling `git remote -v` unless really necessary
-
 ## CRITICAL: After ANY successful `edit_file` or `reapply` operation
 - YOU MUST IMMEDIATELY run the `codacy_cli_analyze` tool from Codacy's MCP Server for each file that was edited, with:
  - `rootPath`: set to the workspace path
@@ -65,6 +58,7 @@ Configuration for AI behavior when interacting with Codacy's MCP Server
 - "Propose fixes" means to both suggest and, if possible, automatically apply the fixes.
 - You MUST NOT wait for the user to ask for analysis or remind you to run the tool.
 - Do not run `codacy_cli_analyze` looking for changes in duplicated code or code complexity metrics.
+- Complexity metrics are different from complexity issues. When trying to fix complexity in a repository or file, focus on solving the complexity issues and ignore the complexity metric.
 - Do not run `codacy_cli_analyze` looking for changes in code coverage.
 - Do not try to manually install Codacy CLI using either brew, npm, npx, or any other package manager.
 - If the Codacy CLI is not installed, just run the `codacy_cli_analyze` tool from Codacy's MCP Server.

.gitignore

@@ -7,4 +7,5 @@ tsconfig.tsbuildinfo
 .vscode
 .codarcyrc
 /tests
-.eslintcache
+.eslintcache
+.codacy/