feat(upgrade) Check version when determining to run RestoreGlossaryIndices step

[chriscollins3456]

Previously, we would only check that the datahub upgrade urn existed for the restore glossary indices step to determine if we should run the step. If it existed we did not run, and if not, we ran it.

Now, we may have situations where someone may have run the upgrade step but we want them to run it again, so we can check a version! The DataHubUpgradeRequest aspect was already storing a version, and for this step we previously set it to 0. Now we check to get that aspect, and if it exists, and it has the same version as the const at the top of the file, skip the step. If it doesn't exist or the version is different, run the step.

Now to have users re-run the step we just need to change the VERSION at the top of the file. I do so here as we know we want some users to re-run this step.

Adds a new test for running with a new version (the diff looks confusing there)

Checklist

• The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
• Links to related issues (if applicable)
• Tests for the changes have been added/updated (if applicable)
• Docs related to the changes have been added/updated (if applicable). If a new feature has been added a Usage Guide has been added for the same.
• For any breaking change/potential downtime/deprecation/big changes an entry has been made in Updating DataHub

[dexter-mh-lee]

LGTM

[github-actions]

Unit Test Results (build & test)

382 tests  +1   382 ✔️ +1   9m 3s ⏱️ + 5m 20s
  89 suites ±0       0 💤 ±0 
  89 files   ±0       0 ❌ ±0 

Results for commit b095e16. ± Comparison against base commit b4bf1d4.

♻️ This comment has been updated with latest results.