[MJAVADOC-649] javadoc:aggregate mis-determines whether a submodule was skipped

**[Robert Varga](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=nite)** opened **[MJAVADOC-649](https://issues.apache.org/jira/browse/MJAVADOC-649?redirect=false)** and commented

The fix for MJAVADOC-613 ends up mis-detecting when a submodule is being skipped in case there is an interplay between command-line and profile activation.

In OpenDaylight we have a setup, where we have a profile doing roughly:

```java

q

true

```

this profile is defined for each and every artifact we build.

We then have a job dedicated to extraction of javadoc which does:

```
mvn verify javadoc:aggregate -e -Pq -Dmaven.javadoc.skip=false
```

This works perfectly well with maven-javadoc-plugin-3.1.1, but breaks with 3.2.0: while each submodule generates its javadoc correctly (observing the command-line override of the profile), the aggregate goal ends up skipping all submodules, resulting in no aggregate being generated.

---

**Affects:** 3.2.0

**Issue Links:**
- [MJAVADOC-613](https://issues.apache.org/jira/browse/MJAVADOC-613) Exclude some modules with aggregate goals
(_**"is caused by"**_)

Reproduce the reported command, `mvn verify javadoc:aggregate -e -Pq -Dmaven.javadoc.skip=false`, using the profile setup and compare behavior between plugin versions 3.1.1 and 3.2.0. Trace the `javadoc:aggregate` handling of submodule skip status; done means the command-line override is honored and an aggregate Javadoc is generated for the eligible submodules.

Written by the indexing model from the issue text.