error when JAVA_HOME is set to invalid value (DAT-10545)

[StevenMassaro]

Impact

• Bug fix (non-breaking change which fixes expected existing functionality)
• Enhancement/New feature (adds functionality without impacting existing logic)
• Breaking change (fix or feature that would cause existing functionality to change)

Description

Throw an error and fail to start Liquibase if the JAVA_HOME environment variable is set and the path it points to does not exist.

Things to be aware of

Things to worry about

If there is an edge case we didn't think about or test for, this will prevent Liquibase from starting in those scenarios.

Additional Context

[github-actions]

Unit Test Results

  4 608 files  ±0    4 608 suites  ±0   41m 13s ⏱️ + 4m 42s
  4 589 tests ±0    4 375 ✔️ ±0     214 💤 ±0  0 ❌ ±0 
54 240 runs  ±0  49 232 ✔️ ±0  5 008 💤 ±0  0 ❌ ±0 

Results for commit 6ec6897. ± Comparison against base commit 83faa21.

♻️ This comment has been updated with latest results.

[nvoxland]

Looks good. Both bash and batch only trigger the "does the file exist" check if JAVA_HOME is set so it won't break people not setting JAVA_HOME and relying on their PATH