[8.18] (backport #17924) Move logstash release information to .ci

[mergify]

Consumers of this information are already cloning the .ci repo. They subsequently curl logstash for this information. Moving to .ci reduces steps and removes the need to track this across information in active streams of logstash.

Issue described in https://github.com/elastic/ingest-dev/issues/4773

---

This is an automatic backport of pull request #17924 done by Mergify.

[mergify]

Cherry-pick of 95a0466 has failed:

On branch mergify/bp/8.18/pr-17924
Your branch is up to date with 'origin/8.18'.

You are currently cherry-picking commit 95a0466d.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Unmerged paths:
  (use "git add/rm <file>..." as appropriate to mark resolution)
	deleted by them: ci/logstash_releases.json

no changes added to commit (use "git add" and/or "git commit -a")

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

[elastic-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarQube

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: 4bef2f7

cc @donoghuc