Dependency version change that fixes compilation error triggers multiple feature generation calls

[TrevCraw]

If there is a compilation error in a Java file and an updated dependency version fixes that compilation error, feature generation is called at least twice. We should find a way to only call feature generation once.

Steps to reproduce:

1. Use the demo devmode project
2. Change the pom.xml or build.gradle MicroProfile umbrella dependency version to 3.2
3. Use mvn liberty:dev or gradle libertyDev to start up dev mode
4. Add SystemLivenessCheck.java as the demo devmode instructions show
5. Notice there is a compilation error and feature generation does not run
6. Update the MicroProfile umbrella dependency version to 4.1
7. Notice the source code now compiles and feature generation is called twice. The first time is an optimize call from the dependency change and the second time is an increment call from the class file change

Debug output: debug-output.txt