Backporting for 2.492.2 LTS

[krisstern]

Latest core version: jenkins-2.497

Postponed
---------

JENKINS-75224           Minor                   1948.v0f99403fe86a_
        Remove support for ?jsonp parameter from Flavor.JSON in Stapler
        https://issues.jenkins.io/browse/JENKINS-75224

Fixed
-----

JENKINS-75265           Minor                   Sun, 16 Feb 2025 06:36:32 +0000
        l:task notifications not working
        regression
        https://issues.jenkins.io/browse/JENKINS-75265

JENKINS-75259           Minor                   Sun, 16 Feb 2025 06:35:59 +0000
        Job start time and remaining time gone from root build history widget for freestyle jobs
        regression
        https://issues.jenkins.io/browse/JENKINS-75259

JENKINS-75255           Major                   Sun, 16 Feb 2025 06:35:39 +0000
        AccessDeniedException from AtomicFileWriter.move (e.g., while fingerprinting) on Windows
        regression
        https://issues.jenkins.io/browse/JENKINS-75255

JENKINS-75163           Minor                   2.494
        Yesterday's builds are shown to be today in build history widget
        https://issues.jenkins.io/browse/JENKINS-75163

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

@timja @basil @MarkEWaite @NotMyFault @mawinter69 @jglick

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]

@krisstern could you update the PR description with the backport details please?

[krisstern]

@krisstern could you update the PR description with the backport details please?

@timja Sure, done

[MarkEWaite]

Thanks!

[A1exKH]

LGTM.