Backporting for LTS 2.452.2 (part 2)

[MarkEWaite]

Backporting for LTS 2.452.2 (part 2)

Backports of two pull requests included in Jenkins 2.461.

• [JENKINS-73047] Fix weather icons  #9227
• Bump org.jenkins-ci.plugins:bouncycastle-api from 2.30.1.77-225.v26ea_c9455fd9 to 2.30.1.78.1-233.vfdcdeb_0a_08a_a_ #9326

Latest core version: jenkins-2.459

Fixed
-----

JENKINS-73047           Minor                   2.461
        Strokes in most weather icons are too wide in Safari when the page is zoomed in (regression in 2.375)
        https://issues.jenkins.io/browse/JENKINS-73047

JENKINS-73252           Minor                   2.457
        Update bundled bouncycastle-api to 2.30.1.78.1-233.vfdcdeb_0a_08a_a_
        https://issues.jenkins.io/browse/JENKINS-73252

Proposed changelog entries

• Fix width of weather icons in Safari when zoomed.
• Include most recent bouncycastle API plugin 2.30.1.78.1-233.vfdcdeb_0a_08a_a_.

Proposed upgrade guidelines

N/A

Testing done

Confirmed that automated tests pass.

Confirmed that 2.30.1.78.1-233.vfdcdeb_0a_08a_a_ bouncycastle API plugin version is bundled in the war file.

Submitter checklist

Beta 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

@krisstern

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

Maintainer checklist

Beta 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).