Update operating system end of life data

[MarkEWaite]

Update operating system end of life data

Adds data for:

• Alpine Linux 3.19
• Amazon Linux 2 (already end of life for Jenkins)
• Amazon Linux 2023
• Fedora 39

Includes test data for more Linux operating systems that were already included in the end of life data.

While answering a question, I was surprised that Amazon Linux 2 had not been listed as a derivative of Red Hat Enterprise Linux 7. It is a derivative of RHEL 7 and is covered by the Jenkins end of life for RHEL 7 derivatives. It has the same version of OpenSSH as RHEL 7.

Testing done

Automated tests pass

Created a Docker container with Amazon Linux 2 and confirmed that the "end of life" message appears as shown in the screenshot.

Proposed changelog entries

• Update operating system end of life data for Amazon Linux, Alpine Linux, and Fedora Linux.

Proposed upgrade guidelines

N/A

Submitter checklist

Preview Give feedback

1. The Jira issue, if it exists, is well-described.
2. The changelog entries and upgrade guidelines are appropriate for the audience affected by the change (users or developers, depending on the change) and are in the imperative mood (see examples). Fill in the Proposed upgrade guidelines section only if there are breaking changes or changes that may require extra steps from users during upgrade.
3. There is automated testing or an explanation as to why this change has no tests.
4. New public classes, fields, and methods are annotated with @Restricted or have @since TODO Javadocs, as appropriate.
5. New deprecations are annotated with @Deprecated(since = "TODO") or @Deprecated(forRemoval = true, since = "TODO"), if applicable.
6. New or substantially changed JavaScript is not defined inline and does not call eval to ease future introduction of Content Security Policy (CSP) directives (see documentation).
7. For dependency updates, there are links to external changelogs and, if possible, full differentials.
8. For new APIs and extension points, there is a link to at least one consumer.

Desired reviewers

N/A

Before the changes are marked as ready-for-merge:

Maintainer checklist

Preview Give feedback

1. There are at least two (2) approvals for the pull request and no outstanding requests for change.
2. Conversations in the pull request are over, or it is explicit that a reviewer is not blocking the change.
3. Changelog entries in the pull request title and/or Proposed changelog entries are accurate, human-readable, and in the imperative mood.
4. Proper changelog labels are set so that the changelog can be generated automatically.
5. If the change needs additional upgrade steps from users, the upgrade-guide-needed label is set and there is a Proposed upgrade guidelines section in the pull request title (see example).
6. If it would make sense to backport the change to LTS, a Jira issue must exist, be a Bug or Improvement, and be labeled as lts-candidate to be considered (see query).

[timja]

/label ready-for-merge

---

This PR is now ready for merge, after ~24 hours, we will merge it if there's no negative feedback.

Thanks!