warn if XSD version does not match build version in validate command (DAT-9874)

[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

Warn if specified XSD version is different than the version of the build when running the validate command.

Things to be aware of

I made this change in a way that this check is "best effort". It should not ever cause a user to experience an uncaught exception.

Things to worry about

It is possible that the regex I'm using is not robust enough to properly get the version out of the XSD URL. It is also possible that there is a better way to do this than using a regex.

Additional Context

[github-actions]

Unit Test Results

  4 548 files  ±    0    4 548 suites  ±0   34m 35s ⏱️ + 2m 4s
  4 541 tests +  10    4 327 ✔️ +  10     214 💤 ±0  0 ❌ ±0 
53 784 runs  +120  48 776 ✔️ +120  5 008 💤 ±0  0 ❌ ±0 

Results for commit 26f322c. ± Comparison against base commit 17ac81c.

♻️ This comment has been updated with latest results.

[nvoxland]

I’m not sure this is a good idea?

People usually have a large set of “previous” change logs that have built up over the years. Like a v1.0.xml and v1.1.xml … v8.3.xml

All those old versions were working fine, including the xsd they are referencing. Ideally as you move on to new changelog files you shouldn't be updating those old files, but this change will bother them until they do.

I get that people can have issues if they don't notice that they are on an old xsd, but we are also now suggesting they don't use a versioned xsd and instead use -latest unless they have a good reason. Under that best practice, this warning makes even less sense because they have picked a specific version for a reason and so even less of a “warning “ ?

[StevenMassaro]

I’m not sure this is a good idea?

People usually have a large set of “previous” change logs that have built up over the years. Like a v1.0.xml and v1.1.xml … v8.3.xml

All those old versions were working fine, including the xsd they are referencing. Ideally as you move on to new changelog files you shouldn't be updating those old files, but this change will bother them until they do.

I get that people can have issues if they don't notice that they are on an old xsd, but we are also now suggesting they don't use a versioned xsd and instead use -latest unless they have a good reason. Under that best practice, this warning makes even less sense because they have picked a specific version for a reason and so even less of a “warning “ ?

We're going to display this message only when running the validate command, and display it at an info level.