NoSuchMethodError: 'void org.apache.maven.doxia.sink.Sink.verbatim()'

### Affected version

3.7.0,3.8.0,3.9.0

### Bug description

Stacktrace in build output hides a run failure that cuts the report: for example [dependency-info is cut after Maven coordinates in 3.7.0](https://maven.apache.org/plugins-archives/maven-project-info-reports-plugin-3.7.0/dependency-info.html) instead of normal [list of coordinates before](https://maven.apache.org/plugins-archives/maven-project-info-reports-plugin-3.6.2/dependency-info.html)

Here are the strack trace that affects 5 reports from MPIR:
1.
```
[INFO] Generating "Maven Coordinates" report --- maven-project-info-reports-plugin:3.8.0:dependency-info
[WARNING] An issue has occurred with maven-project-info-reports-plugin:3.8.0:dependency-info report, skipping LinkageError 'void org.apache.maven.doxia.sink.Sink.verbatim()', please report an issue to Maven dev team.
java.lang.NoSuchMethodError: 'void org.apache.maven.doxia.sink.Sink.verbatim()'
at org.apache.maven.reporting.AbstractMavenReportRenderer.verbatimText (AbstractMavenReportRenderer.java:346)
at org.apache.maven.report.projectinfo.DependencyInformationReport$DependencyInformationRenderer.renderDependencyInfo (DependencyInformationReport.java:217)
at org.apache.maven.report.projectinfo.DependencyInformationReport$DependencyInformationRenderer.renderMavenPluginCoordinates (DependencyInformationReport.java:156)
at org.apache.maven.report.projectinfo.DependencyInformationReport$DependencyInformationRenderer.renderBody (DependencyInformationReport.java:135)
at org.apache.maven.reporting.AbstractMavenReportRenderer.render (AbstractMavenReportRenderer.java:76)
at org.apache.maven.report.projectinfo.DependencyInformationReport.executeReport (DependencyInformationReport.java:87)
at org.apache.maven.reporting.AbstractMavenReport.generate (AbstractMavenReport.java:358)
```

2.
```
[INFO] Generating "CI Management" report --- maven-project-info-reports-plugin:3.8.0:ci-management
[WARNING] An issue has occurred with maven-project-info-reports-plugin:3.8.0:ci-management report, skipping LinkageError 'void org.apache.maven.doxia.sink.Sink.verbatim()', please report an issue to Maven dev team.
java.lang.NoSuchMethodError: 'void org.apache.maven.doxia.sink.Sink.verbatim()'
at org.apache.maven.reporting.AbstractMavenReportRenderer.verbatimLink (AbstractMavenReportRenderer.java:367)
```

3.
```
[INFO] Generating "Issue Management" report --- maven-project-info-reports-plugin:3.8.0:issue-management
[WARNING] An issue has occurred with maven-project-info-reports-plugin:3.8.0:issue-management report, skipping LinkageError 'void org.apache.maven.doxia.sink.Sink.verbatim()', please report an issue to Maven dev team.
java.lang.NoSuchMethodError: 'void org.apache.maven.doxia.sink.Sink.verbatim()'
at org.apache.maven.reporting.AbstractMavenReportRenderer.verbatimLink (AbstractMavenReportRenderer.java:367)
```

4.
```
[INFO] Generating "Licenses" report --- maven-project-info-reports-plugin:3.8.0:licenses
[WARNING] An issue has occurred with maven-project-info-reports-plugin:3.8.0:licenses report, skipping LinkageError 'void org.apache.maven.doxia.sink.Sink.verbatim()', please report an issue to Maven dev team.
java.lang.NoSuchMethodError: 'void org.apache.maven.doxia.sink.Sink.verbatim()'
at org.apache.maven.reporting.AbstractMavenReportRenderer.verbatimText (AbstractMavenReportRenderer.java:346)
```

5.
```
[INFO] Generating "Source Code Management" report --- maven-project-info-reports-plugin:3.8.0:scm
[WARNING] An issue has occurred with maven-project-info-reports-plugin:3.8.0:scm report, skipping LinkageError 'void org.apache.maven.doxia.sink.Sink.verbatim()', please report an issue to Maven dev team.
java.lang.NoSuchMethodError: 'void org.apache.maven.doxia.sink.Sink.verbatim()'
at org.apache.maven.reporting.AbstractMavenReportRenderer.verbatimLink (AbstractMavenReportRenderer.java:367)
```

Start at AbstractMavenReportRenderer.verbatimText and verbatimLink, then trace the five affected report renderers named in the stack traces. Check the Maven/Doxia API compatibility involved and verify that dependency-info, ci-management, issue-management, licenses, and scm generate complete reports without the NoSuchMethodError.

Written by the indexing model from the issue text.