Changes to files in nested utility project need not always restart module

Changes to a .class file inside a nested utility project currently marks the module as requiring a restart, because the application server won't pick up those changes without a restart.

When running in debug mode, though, the debugger will use the new classes as changed in the workspace, so a restart of a module is slow and costly.

The fix (for now) would be to only restart the web module if the publish is a full publish, or, if the nested archive's deployment name matches the strings in the server editor's restart-module regex clause.

Example project replicating the bug can be found at https://github.com/maxandersen/JBIDE-17724

Unzip the attached project structure (stripped down from an existing project)
Run 'mvn clean install eclipse:clean eclipse:eclipse' at the root
Import existing projects into eclipse luna with JBoss Tools
Deploy to a "JBoss Enterprise Application Platform 5.x" runtime
Make a change to MyController.java inside the project-war webapp => the change is hot deployed
Make a change to MySecondController.java inside the project-module dependency => the full WAR is undeployed then redeployed