Figure out how to make the AppInfo test not fail if in wrong test phase

[jetmore]

The AppInfo_IntegrationTest requires build artifacts that are created by a maven plugin, so it often fails if run from inside eclipse and the properties happen not to exist. Could we do something like

• implement a new test phase that only runs after properties are built/copied
• add a check in the test to see what phase we're running in (that seems like the impossible one). Or maybe mvn could set an environment variable and we only run in mvn?
• If we don't think we're running in the correct phase, just skip the test (see https://www.baeldung.com/junit-conditional-assume, assumeThat)