javadoc build errors under jdk17.0.7

[starksm64]

While testing out a new linux system, I tried building the current cdi master and found a few errors due to javadoc issues. This builds fine under jdk11, but the errors seem correct so I assume the checking has gotten stricter.

These are the 5 errors I see:

/home/starksm/Dev/Jakarta/cdi/api/src/main/java/jakarta/decorator/package-info.java:35: error: heading used out of sequence: <H3>, compared to implicit preceding heading: <H1>
 * <h3>Decorated types</h3>
   ^
/home/starksm/Dev/Jakarta/cdi/api/src/main/java/jakarta/enterprise/context/package-info.java:32: error: heading used out of sequence: <H3>, compared to implicit preceding heading: <H1>
 * <h3>Built-in scopes</h3>
   ^
/home/starksm/Dev/Jakarta/cdi/api/src/main/java/jakarta/enterprise/event/package-info.java:40: error: heading used out of sequence: <H3>, compared to implicit preceding heading: <H1>
 * <h3>Event objects and event types</h3>
   ^
/home/starksm/Dev/Jakarta/cdi/api/src/main/java/jakarta/enterprise/inject/spi/package-info.java:31: error: heading used out of sequence: <H3>, compared to implicit preceding heading: <H1>
 * <h3>The <code>BeanManager</code> object</h3>
home/starksm/Dev/Jakarta/cdi/api/src/main/java/jakarta/enterprise/event/Observes.java:109: error: unexpected end tag: </p>
 * </p>

There are also a ton of warnings about no comments that can be addressed later.

[Emily-Jiang]

I have seen this one before. I think the simple fix is to update to h2, which is valid under Java 17.

[Emily-Jiang]

ah, I saw your PR now. +1