fix(docs): ensure alias is applied to versioned releases

[sthulb]

Issue number: #2628

Summary

Changes

Please provide a summary of what's being changed

Ensures that the JQ voodoo inserts the alias.

User experience

Please share what the user experience looks like before and after this change

Before:
Alias wasn't inserted into the versions.json unless it was a new version number,

After:
alias is added to the targeted version number or new version number

Checklist

If your change doesn't seem to apply, please leave them unchecked.

• Meet tenets criteria
• I have performed a self-review of this change
• Changes have been tested
• Changes are documented
• PR title follows conventional commit semantics

Is this a breaking change?

RFC issue number:

Checklist:

• Migration process documented
• Implement warnings (if it can live side by side)

Acknowledgment

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.

[heitorlessa]

looking...👀 as on-call is busy with Pydantic v2

[github-actions]

No related issues found. Please ensure there is an open issue related to this change to avoid significant delays or closure.

[sthulb]

input file:

[
  {
    "title": "2.19.0",
    "version": "2.19.0",
    "aliases": []
  },
  {
    "title": "2.18.0",
    "version": "2.18.0",
    "aliases": []
  }
]

output with same version number:

[
  {
    "title": "2.19.0",
    "version": "2.19.0",
    "aliases": [
      "latest"
    ]
  },
  {
    "title": "2.18.0",
    "version": "2.18.0",
    "aliases": []
  }
]

output with new version number:

[
  {
    "title": "2.20.0",
    "version": "2.20.0",
    "aliases": [
      "latest"
    ]
  },
  {
    "title": "2.19.0",
    "version": "2.19.0",
    "aliases": []
  },
  {
    "title": "2.18.0",
    "version": "2.18.0",
    "aliases": []
  }
]