Remove key rotation banner from weekly release page

[NotMyFault]

The warning has been removed from the carousel at jenkins.io some time ago. I propose to remove it from this repository too.
The current LTS line, 2.401, will continue showing the warning, given it's the first new LTS line with the updated key.

[timja]

won't these get updated on the next LTS point release?

[NotMyFault]

won't these get updated on the next LTS point release?

If someone chooses to merge master into stable-2.401, yes. But given this is non-backportable, this shouldn't happen.

[basil]

Our current (informal) process followed in e.g. #202 has historically involved merging the main branch into stable branches. Introducing non-backportable PRs seems error-prone in that it would be all too easy for someone to follow past precedent without realizing that there is a non-backportable PR, especially if there is no way for a first-time release lead to identify such non-backportable PRs.

[NotMyFault]

Our current (informal) process followed in e.g. #202

This was almost 2 1/2 years ago. There's no item on the current LTS checklist that states that master should be merged into a stable-x branch.
Everything goes through backporting from Jira (or GH issues, if applicable). Given I didn't file an issue to backport this PR, no action should be taken for 2.401.2/3(/4).

[basil]

My point is that the current release scheme, in which stable branches are created from the main branch periodically, does not really support displaying different text for different branches (#386). If the text on stable-2.387 intentionally diverged from the text on the main branch, that intentional divergence would be lost again when stable-2.401 was created from the main branch just a few months later. The only functional purpose for stable branches in this repository at this time is to decrease the risk associated with last-minute code changes, not to display different text for different branches.