67 move config validation to before lock file is acquired

[Lagejohn]

E2E tests passed successfully.

Manually tested by leaving XML config key table.runHistoryFile.URI (old version of table.runHistoryFile.path) in place and testing before and after.

Previous behavior:

Exception in thread "main" java.lang.NullPointerException
	at java.base/java.util.Objects.requireNonNull(Objects.java:209)
	at java.base/sun.nio.fs.UnixFileSystem.getPath(UnixFileSystem.java:263)
	at java.base/java.nio.file.Path.of(Path.java:147)
	at java.base/java.nio.file.Paths.get(Paths.java:69)
	at edu.jhuapl.sd.sig.mmtc.cfg.MmtcConfig.getRunHistoryFilePath(MmtcConfig.java:737)
	at edu.jhuapl.sd.sig.mmtc.cfg.MmtcConfig.getLockFileLocation(MmtcConfig.java:995)
	at edu.jhuapl.sd.sig.mmtc.cfg.MmtcConfig.acquireLockFile(MmtcConfig.java:1001)
	at edu.jhuapl.sd.sig.mmtc.app.MmtcCli.main(MmtcCli.java:113)

New behavior:

Exception in thread "main" edu.jhuapl.sd.sig.mmtc.app.MmtcException: MMTC correlation initialization failed.
	at edu.jhuapl.sd.sig.mmtc.app.MmtcCli.main(MmtcCli.java:111)
Caused by: edu.jhuapl.sd.sig.mmtc.app.MmtcException: Failed to validate TimeCorrelationConfigProperties.xml, missing 1 required key(s): [table.runHistoryFile.path]
	at edu.jhuapl.sd.sig.mmtc.cfg.MmtcConfig.validate(MmtcConfig.java:1423)
	at edu.jhuapl.sd.sig.mmtc.app.MmtcCli.main(MmtcCli.java:108)
MMTC correlation initialization failed.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[github-advanced-security]

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

• The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
• Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
• You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.

[rmseng]

LGTM