Fix validate misbehavior in cucumber tests

[al-niessner]

🗒️ Summary

Check for internal errors and use latest validate

⚙️ Test Data and/or Report

See automated unit testing below or run cucumber tests if not automated yet.

♻️ Related Issues

Closes #822

[al-niessner]

@jordanpadams waiting for review on NASA-PDS/validate#1057 to see if it fixes this problem. Using validate project for this instead of maven artifact in eclipse makes a giant mess as it tries to run both cucumbers simultaneously then complains about it. So I need the latest validate artifact.

[al-niessner]

@jordanpadams @nutjob4life @tloubrieu-jpl

All tests work now. I had to re-enable one of the tests validate.feature tests, but they all work independently as they do together. The schema(tron) mole (le Carre style) was the culprit here too.

[al-niessner]

Is this a weird problem where the github actions is not pulling the very latest snapshot because it thinks it already has it?

[nutjob4life]

@al-niessner yes it is; do you have a link to the GitHub Actions run?

[al-niessner]

@nutjob4life

I do not understand the question, so no. I can click on details and ask it to run all jobs again. I did that and it seems to have made them all pass. Or an angel did something for me that I will never ask about. Exactly why you teach people to fish not give them a fish.

[nutjob4life]

@al-niessner hey I'm happy not to look the gift horse in the mouth—whatever that means! Let's press on!