Investigate build file change logic for dev mode

[kathrynkodama]

Investigative item for: https://github.com/OpenLiberty/ci.maven/blob/3794a79621af66a45761e1e5a8cbfa108e42eb90/liberty-maven-plugin/src/main/java/io/openliberty/tools/maven/server/DevMojo.java#L813

In ci.gradle we do not call the deploy task on compile dependency changes. Further investigation may be required into why the compile dependency change logic differs between ci.maven and ci.gradle. See https://github.com/OpenLiberty/ci.maven/issues/611#issuecomment-537766352 for why we redeploy on compile dependency change in ci.maven.

We should also investigate if there are duplicate scenarios where install-feature may be called, for example a compile dependency change that triggers a new feature to be generated at the same time an esa dependency or the plugin configuration is modified.