Code Review: Persists ESLint-suppressed findings as accepted issues but triggers a crash in `saveAcceptedIssueResolution` when encountering a line number of 0.

1. ⚠️ Bug: saveAcceptedIssueResolution crashes when issue.getLine() is 0
   Files: sonar-plugin/sonar-javascript-plugin/src/main/java/org/sonar/plugins/javascript/analysis/AnalysisProcessor.java:654

   In `saveAcceptedIssueResolution` (line 654), `file.selectLine(issue.getLine())` is called unconditionally. If a suppressed issue has `line == 0` (the protobuf default for unset int32 fields), this will throw an `IllegalArgumentException` because SonarQube line indexing is 1-based. The existing `saveIssue` method at line 485 has a guard (`issue.getLine() != 0`) before calling `selectLine`, but `saveAcceptedIssueResolution` lacks this check. While the try/catch in `saveSuppressedIssues` will prevent a crash, the issue resolution will silently fail to save.

   Fix (Add a guard for line == 0 before calling selectLine, matching the pattern in saveIssue):
   private void saveAcceptedIssueResolution(JsTsContext<?> context, Issue issue, RuleKey ruleKey) {
     if (issue.getLine() == 0) {
       LOG.warn("Cannot save issue resolution for rule {} without a valid line", ruleKey);
       return;
     }
     context
       .getSensorContext()
       .newIssueResolution()
       .on(file)
       .at(file.selectLine(issue.getLine()))
       .status(IssueResolution.Status.DEFAULT)
       .forRules(List.of(ruleKey))
       .comment(issue.getResolutionComment())
       .save();
   }