fix: correct stale Javadoc in getErrorPatternLines()

Remove references to RuboCop-specific patterns (offense, offenses, C:/W:/E:/F:
severity prefixes) from the Javadoc — these were removed when ERROR_PATTERN was
simplified to universal keywords (error, exception, failed, fatal).

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Author: lidiams96

src/main/java/io/jenkins/plugins/explain_error/PipelineLogExtractor.java

@@ -122,9 +122,8 @@ private List<String> readLimitedLog(AnnotatedLargeText<? extends FlowNode> logTe
      * or when errors appear early in a large build log and would be missed by the
      * last-N-lines approach.
      * <p>
-     * Matched patterns include: {@code error}, {@code exception}, {@code failed},
-     * {@code offense}/{@code offenses} (RuboCop), {@code fatal}, and RuboCop offense
-     * lines ({@code C:}, {@code W:}, {@code E:}, {@code F:} followed by a line number).
+     * Matched patterns include: {@code error}, {@code exception}, {@code failed}, and
+     * {@code fatal} (case-insensitive, word-boundary anchored).
      *
      * @return list of error-context lines (ordered as they appear in the log),
      *         or an empty list if no patterns are found or the log cannot be read