[FEATURE] Support runtime view technologies

The analyzer appears to falsely list a number of dependencies as Unused, such as JSP, JSTL and Thymeleaf. This is presumably because they are not used during compile of java assets. (note that javax/jakarta JSP is defined as 'runtime' but JSTL and Thymeleaf have to be scope=compile)

There are plugins, such as the io.leonard.maven.plugins jspc maven plugin, which can e used to compile JSP's during local build and thus making them available for analysis. It would be a big benefit if depclean could invoke those plugins to compile those jsp and html files (Thymeleaf) so they can be analyzed and thus reduce the number of false positives flagged as unused.

No source files or tests are named. Start by tracing how depclean analyzes compiled Java assets and Maven dependency scopes, then study how the io.leonard.maven.plugins jspc Maven plugin could expose JSP and view files to that analysis. Done means JSP, JSTL, and Thymeleaf dependencies used by runtime views are no longer falsely reported as unused.

Written by the indexing model from the issue text.