Fix empty dependency exclusion filtering

[Aayush10016]

Summary

• return an empty result when dependency exclusion patterns are absent
• stop verbose analysis output from reporting real findings again as ignored dependencies
• add integration assertions for both used-undeclared and unused-declared output

Fixes #1645.

Root cause

filterDependencies(...) returned its full input set when the exclusion array was null or empty. Callers treat the return value as the dependencies removed by an exclusion filter, so the full input was incorrectly added to the ignored-dependency sections.

Verification

• regression assertions failed before the production change and passed afterward
• mvn -Prun-its -Dinvoker.test=analyze verify — passed
• mvn -Prun-its verify — passed; 99 integration projects, 0 failures or errors
• unit tests, Checkstyle, Spotless, Apache RAT, compilation, and packaging passed as part of the full build
• git diff --check — passed