Fixed EAR devc loose config context root

[sajeerzeji]

When running libertyDevc for a multi-module EAR project with looseApplication = true, Liberty ignored the configured context root and fell back to using the WAR filename instead.

The root cause was that DevTaskUtil always passed projectDirectory (the EAR subproject directory) as both projectDirectory and multiModuleProjectDirectory in the super() call to DevUtil, causing the container to mount only the EAR subproject as /devmode. But installLooseConfigEar() was already writing loose config paths relative to the root project directory, so all paths inside the container had an extra subproject segment that didn't exist. Meaning Liberty could never find application.xml and its context root mapping.

It now calculates multiModuleProjectDirectory as the root project directory when packaging is EAR and passes it to DevUtil, aligning the container mount with the path substitution root so Liberty can resolve all loose config paths correctly.

I have added IT to test this and also manually tested, the result is as below

1. The browser showing localhost:9090/guide-gradle-multimodules-custmm-war-1.0-SNAPSHOT/: "Context Root Not Found", thus the WAR filename URL no longer works as a fallback

2. The browser showing localhost:9090/converter/: "Converter, Context root is working correctly."

And from the terminal logs,

[AUDIT   ] CWWKT0016I: Web application available (default_host): http://32c7e762d2bf:9090/converter/

And all the devc tests are passed