[8.19] (backport #358) Update buildkite script to look for new logstash releases location

[mergify]

This commit updates the buildkite scripts to look in the .ci repo in the logstash-plugins org for the new location of logstash releases.

Thanks for contributing to Logstash! If you haven't already signed our CLA, here's a handy link: https://www.elastic.co/contributor-agreement/

---

This is an automatic backport of pull request #358 done by [Mergify](https://mergify.com).

[mergify]

Cherry-pick of febb207 has failed:

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

You are currently cherry-picking commit febb207.
  (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 <file>..." to mark resolution)
	both modified:   .buildkite/scripts/build-pipeline/generate-steps.py
	both modified:   .buildkite/scripts/e2e-pipeline/generate-steps.py
	both modified:   .buildkite/scripts/pull-request-pipeline/generate-steps.py
	both modified:   .buildkite/scripts/run_tests.sh

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

[donoghuc]

Needed a merge conflict resolution. @mashhurs can you double check?

[mashhurs]

LGTM!

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: 9e6a29b

History

• 💔 Build #629 failed fc93299

cc @donoghuc