Use liquibase StringUtil not lang3.StringUtils

[nvoxland]

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

We should be using our StringUtil class, not commons.lang3 versions which are not always available.

Things to be aware of

• Does not change functionality, just changes the method called

Things to worry about

• Nothing

[github-actions]

Unit Test Results

  4 668 files  ±0    4 668 suites  ±0   36m 12s ⏱️ +6s
  4 627 tests ±0    4 401 ✔️ ±0     226 💤 ±0  0 ❌ ±0 
54 528 runs  ±0  49 465 ✔️ ±0  5 063 💤 ±0  0 ❌ ±0 

Results for commit c4bad39. ± Comparison against base commit 59ca536.

[XDelphiGrl]

Fix removes use of the org.apache.commons.lang3.StringUtils.isNotBlank() in favor of liquibase.util.StringUtil.isNotEmpty(). This ensures the Liquibase StringUtil class is used consistently in the DatabaseUtils.java class.

• No additional testing required.

APPROVED