feat: POST endpoint for versions

[mtruj013]

Done

• Added POST endpoint for versions and related tests
• Drive by's:
  • Updated ARTIFACT_TYPES to remove other as an option
  • Updated version schema to replace pro_supported with 2 new fields, esm_pro_supported and break_bug_pro_supported
  • Updated existing tests and helpers to make use of is_hidden version field

QA

• See that tests pass
• For a more thorough QA:
  • Run the site using the command dotrun
  • Add a couple versions and see that everything passes as intended, sample curls here

Issue / Card

https://warthogs.atlassian.net/browse/WD-33168

[britneywwc]

Should we add a check to ensure that release_date will be before the other supported dates? This could be helpful to prevent user errors

i.e this payload goes through

'{
    "release": "2.1.0",
    "architecture": ["amd64"],
    "release_date": {"date": "2028-06-01"},
    "supported": {"date": "2027-06-01"},
    "esm_pro_supported": {"date": "2028-06-01"},
    "break_bug_pro_supported": {"date": "2029-06-01"},
    "legacy_supported": {"notes": "Supported until further notice"}
  }'

[mtruj013]

Thanks @britneywwc, great catch/suggestion. I've added the check and related tests, could you check again?

[Skazitron]

{
    "release": "7.0.0",
    "architecture": ["amd64"],
    "release_date": {"date": "2026-06-01"},
    "supported": {"date": "not-a-real-date"},
    "esm_pro_supported": {"date": "2028-06-01"},
    "break_bug_pro_supported": {"date": "2029-06-01"},
    "legacy_supported": {"notes": "Supported until further notice"}
}

This payload goes through where the date is not a real date. Is this expected behavior?

[mtruj013]

Nope, that's a bug. Thanks for catching!

[Skazitron]

@mtruj013 LGTM!