Update to new release API endpoints

[navyau09]

Release API migration to new endpoints is now complete.

Past Release Endpoint : https://elastic-release-api.s3.us-west-2.amazonaws.com/public/past-releases.json
Future Release Endpoint : https://elastic-release-api.s3.us-west-2.amazonaws.com/public/future-releases.json

This PR updates the old Release API endpoints to new one's

More Info:
https://groups.google.com/a/elastic.co/g/release-eng-team/c/qgXaCX-y29k/m/jzm2S8MeAwAJ

[mergify]

This pull request does not have a backport label. Could you fix it @navyau09? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-v./d./d./d is the label to automatically backport to the 8./d branch. /d is the digit
• backport-active-all is the label that automatically backports to all active branches.
• backport-active-8 is the label that automatically backports to all active minor branches for the 8 major.
• backport-active-9 is the label that automatically backports to all active minor branches for the 9 major.

[github-actions]

@Mergifyio backport 8.19 9.2 9.3

[mergify]

backport 8.19 9.2 9.3

✅ Backports have been created

Details

• #3975 [8.19](backport #3935) Update to new release API endpoints has been created for branch 8.19 but encountered conflicts

Cherry-pick of 6563747 has failed:

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

You are currently cherry-picking commit 65637471.
  (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)
	both modified:   .github/workflows/updatecli.yml
	deleted by us:   llm/cve.md

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

• #3976 [9.2](backport #3935) Update to new release API endpoints has been created for branch 9.2 but encountered conflicts

Cherry-pick of 6563747 has failed:

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

You are currently cherry-picking commit 65637471.
  (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)

Changes to be committed:
	modified:   .github/workflows/updatecli.yml

Unmerged paths:
  (use "git add/rm <file>..." as appropriate to mark resolution)
	deleted by us:   llm/cve.md

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

• #3977 [9.3](backport #3935) Update to new release API endpoints has been created for branch 9.3 but encountered conflicts

Cherry-pick of 6563747 has failed:

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

You are currently cherry-picking commit 65637471.
  (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)

Changes to be committed:
	modified:   .github/workflows/updatecli.yml

Unmerged paths:
  (use "git add/rm <file>..." as appropriate to mark resolution)
	deleted by us:   llm/cve.md

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