warn when encountering an obsolete/invalid dependency exclusion

### New feature, improvement proposal

currently it is possible to add any `groupId`/`artifactId` inside an `exclusion` for a given dependency.

However if that exclusion is not within the dependency chain of the specified dependency then no warning is emmited by maven.

Over time this can lead to accumulation of no longer needed exclusions. It would be useful if Maven emitted a log (warning?) about exclusions for a dependency that have no impact.

e.g. given the following `pom.xml`

```xml

4.0.0

test
test
1.0-SNAPSHOT

org.junit.jupiter
junit-jupiter-api
5.11.0


org.apache.continuum
continuum-core

```

running `mvn package -DskipTests` results in no warnings that the apache continuum exclusion is not needed.

it would be nice to have an entry like

`[WARNING] exclusion of org.apache.continuum:continuum-core for org.junit.jupiter:junit-jupiter-api in test:test is obsolete - there is no dependency on this exclusion`

Reproduce the behavior with the supplied pom.xml and `mvn package -DskipTests`, then trace Maven's dependency resolution and exclusion handling from that example. Done means an obsolete exclusion such as `org.apache.continuum:continuum-core` produces a warning identifying the exclusion and declaring that it has no impact.

Written by the indexing model from the issue text.