RAMPART-454 Put servlet-api on the aggregator Javadoc classpath

mvn package (and mvn site / site-deploy) was failing in the apidocs
module with:

  error: package jakarta.servlet.http does not exist
  import jakarta.servlet.http.HttpServletRequest;

because rampart-core references HttpServletRequest (RampartUtil.java)
and declares jakarta.servlet-api with <scope>provided</scope>. Provided
scope is not transitive, so when apidocs aggregates rampart-core's
sources for Javadoc, the servlet API is absent from the Javadoc
classpath.

Declare jakarta.servlet-api explicitly in apidocs/pom.xml so
javadoc-no-fork (invoked at prepare-package for dist-javadoc and at
site for site-javadoc) can resolve the import.

Author: robertlazarski

apidocs/pom.xml

@@ -50,6 +50,14 @@
             <artifactId>rampart-trust</artifactId>
             <version>${project.version}</version>
         </dependency>
+        <!-- rampart-core references jakarta.servlet.http.HttpServletRequest.
+             The servlet API is declared 'provided' in rampart-core so it is
+             not transitively visible; make it available on the Javadoc
+             classpath explicitly. -->
+        <dependency>
+            <groupId>jakarta.servlet</groupId>
+            <artifactId>jakarta.servlet-api</artifactId>
+        </dependency>
     </dependencies>
     <build>
         <plugins>