Introduces releases.yml file

Why is this change being made?

Creates a single source of truth for the next 12 monthly releases. This file includes the version, release dates and release managers information. The dates were automatically calculated by the release_dates gem (https://gitlab.com/gitlab-org/delivery/release_dates/-/merge_requests/1)

The purpose of this file is to:

• Act as a SSOT for absolute release dates
• Be consumed and parsed by different GitLab stakeholders and customers.

Upcoming iterations for this file include generating a static site to display their information in a friendly way, and automate the update this information on a schedule.

Related to #34176 (closed)

Observations

• groupdelivery Until the release_managers.yml file is deprecated or updated based on releases.yml, when updating the release managers' information on releases_managers.yml, we should also copy and paste the same information on releases.yml

How to download the data?

On Ruby:

# Replace the commit with master once this MR has been merged
[33] pry(main)> url = "https://gitlab.com/gitlab-com/www-gitlab-com/-/raw/e8919fbec000e904aa6449e778a4115909038fbc/data/releases.yml"
=> "https://gitlab.com/gitlab-com/www-gitlab-com/-/raw/e8919fbec000e904aa6449e778a4115909038fbc/data/releases.yml"
[34] pry(main)> YAML.safe_load(HTTP.get(url))
=> [{"version"=>"17.2", "date"=>"2024-07-18"},
 {"version"=>"17.1", "date"=>"2024-06-20"},
 {"version"=>"17.0", "date"=>"2024-05-16"},
 {"version"=>"16.11", "date"=>"2024-04-18"},
 {"version"=>"16.10", "date"=>"2024-03-21"},
 {"version"=>"16.9", "date"=>"2024-02-15"},
 {"version"=>"16.8", "date"=>"2024-01-18"},
 {"version"=>"16.7", "date"=>"2023-12-21"},
 {"version"=>"16.6", "date"=>"2023-11-16"},
 {"version"=>"16.5", "date"=>"2023-10-22", "manager_americas"=>["Jenny Kim"], "manager_apac_emea"=>["Ahmad Tolba"], "appsec"=>["Ottilia Westerlund", "Nikhil George"]},
 {"version"=>"16.4", "date"=>"2023-09-22", "manager_americas"=>["Mayra Cabrera"], "manager_apac_emea"=>["Vladimir Glafirov"], "appsec"=>["Félix Veillette-Potvin", "Nick Malcolm"]},
 {"version"=>"16.3", "date"=>"2023-08-22", "manager_americas"=>["Steve Abrams"], "manager_apac_emea"=>["Reuben Pereira"], "appsec"=>["Ameya Darshan", "Dominic Couture"]},
 {"version"=>"16.2", "date"=>"2023-07-22", "manager_americas"=>["John Skarbek"], "manager_apac_emea"=>["Ahmad Tolba"], "appsec"=>["Greg Myers", "Costel Maxim"]}]

Author Checklist

• Provided a concise title for this Merge Request (MR)
• Added a description to this MR explaining the reasons for the proposed change, per say why, not just what
  • Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added, and the content is SAFE
• Assign reviewers for this MR to the correct Directly Responsible Individual/s (DRI)
  • If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the Maintained by section on the page being edited
  • If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies
  • The when to get approval handbook section explains the workflow in more detail
• [-] If the changes affect team members, or warrant an announcement in another way, please consider posting an update in #whats-happening-at-gitlab linking to this MR
  • If this is a change that directly impacts the majority of global team members, it should be a candidate for #company-fyi. Please work with internal communications and check the handbook for examples.

---