Enhance Dashboard refresh logic when build files are generated in the target/build directories

[JoshwinThomasIBM]

To improve the dashboard refresh behaviour for the issue, we've implemented a logic that checks if build files are generated in the target or build directories. When a file is created, we look for any sibling files in the parent directory of the target/build folder. If such files exist, the refresh is skipped; otherwise, the dashboard refresh is triggered. This implementation is done based on the assumption that “target” and "build" are the name for Maven and Gradle output dir respectively and pom.xml and target or build.gradle and build directory are siblings.

However, we now need to find a solution for cases where this assumption does not hold true.

[JoshwinThomasIBM]

About output directory where Maven generates files, the default is target but can be overridden by specifying the directory element in the POM with a custom value. See Maven documentation here: https://maven.apache.org/ref/3.9.9/maven-model/maven.html#class_build for the formal description(s) on output directory overrides.