Updated "Change Set" wording to "Changeset"

[kataggart]

Changeset Consistency Naming conventions

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

Our style guide has "changeset" being the correct term vs. "change set". This updates all the usage of "change set" to match the standard.

Example Of Change

Run liquibase history against a database that has been updated by at least one changeset
Run liquibase status against a database that has at least one changeset needed to be updated.

Actual Behavior

The history command uses the name changesets
Database updated at 1/28/22, 4:53 PM. Applied 97 changeset(s) in 82.304s, DeploymentId: 3410389992

The status command calls uses the name change sets
2 change sets have not been applied to

Expected/Desired Behavior

Both commands use the same "changeset" terminology

Fixes #3041

[github-actions]

Unit Test Results

  4 608 files  ±0    4 608 suites  ±0   29m 58s ⏱️ - 1m 23s
  4 578 tests ±0    4 360 ✔️ ±0     218 💤 ±0  0 ❌ ±0 
54 108 runs  ±0  49 096 ✔️ ±0  5 012 💤 ±0  0 ❌ ±0 

Results for commit 920cb4b. ± Comparison against base commit dd17e53.

♻️ This comment has been updated with latest results.

[nvoxland]

I did a search for all uses of "change set" and fixed them all

[XDelphiGrl]

• This PR has no functional impact.
  • Standardizes changeset terminology in code comments and console messages.

APPROVED

Passing Functional Tests
Passing Test Harness Execution