Do not throw a confusing error if a datatype specified as a changelog parameter is not expanded

[nvoxland]

Description

If a user specifies something that looks like a changelog parameter but doesn't match a specified parameter, liquibase simply users it as-is.

However, the DataType.fromDescription function that is used to determine the actual datatype to return cannot correctly handle a datatype that is formatted like a changelog parameter.

This fixes the datatype handling so it handles a datatype that looks like ${ ... } as just a datatype it doesn't understand.

Example Problem Changeset

<createTable tableName="test_table">
    <column name="id" type="${invalid}"/>
</createTable>

Current behavior

Throws an ArrayIndexOutOfBoundsException exception

Fixed behavior

Fails with an error like Syntax error in SQL statement "CREATE TABLE test_table (id ${INVALID } which allows the user to recognize that they did not correctly set the changelog parameter

[github-actions]

Unit Test Results

  4 512 files    4 512 suites   39m 1s ⏱️
  4 375 tests   4 161 ✔️    214 💤 0 ❌
51 780 runs  46 772 ✔️ 5 008 💤 0 ❌

Results for commit aa5bdd8.

[XDelphiGrl]

• Fix is straightforward and improves user experience.
• New unit test added.
• No additional testing necessary.

These changes have no impact on harness or functional tests.

[XDelphiGrl]

Approved.