[Fleet] Download Agent link points to prior release page

[EricDavisX]

Noted a few times and finally cited and discussed with some attention. Copying most text from slack:

a PM Found a weird glitch with fleet - when you navigate in kibana to add an agent, the first step is, of course, Download the Elastic Agent to your host- however, now it points to the wrong place
https://www.elastic.co/downloads/past-releases/elastic-agent-7-14-0

rather than
https://www.elastic.co/downloads/elastic-agent

...the latter will always point to 'current' which is a pain when we are doing the month long BC process and the 'newly coming almost released' version isn't actually shipped yet, so the download links all point to the prior version Agent. This was updated purposefully to correct that, but seems to have this undesired side effect. And maybe we can fix it / do better. See more below.

Engg confirmed that the changes in the below ticket did affect this on purpose: #102491

Another relating:
#104494 (comment)

Engg Citation on possible fix:
If we can get a new route on elastic.co like /downloads/elastic-agent/version and have the server determine whether to redirect to the latest release or the past release page, that would be ideal. Kibana ought not to have to run a query to find out what the latest release is.

[elasticmachine]

Pinging @elastic/fleet (Team:Fleet)

[jen-huang]

Yep, this was an intentional change and we knew it would be a pain in development prior to releases being published, but it's a better experience for users running older releases. It is not a wrong link as these pages are the only ones we have available that has links to previous version downloads.

@mostlyjason I wonder if we should involve marketing in setting up the suggested elastic.co/downloads/elastic-agent/{VERSION} that either redirects to a prior release download page vs current release page?

I'm putting this in the backlog for now.