Upgrade bundled plugins

[basil]

Our usual policy is not to update bundled plugins without a specific reason, such as a security fix. In this case the specific reason is the same as that of #8134, #7341, #7324, and #7175: to mitigate the impact of JENKINS-69361.

Testing done

Ran mvn clean verify -Dtest=jenkins.install.LoadDetachedPluginsTest,jenkins.model.StartupTest (including un-ignored LoadDetachedPluginsTest#noUpdateSiteWarnings) locally.

Proposed changelog entries

Update several bundled plugins to the latest versions.

Proposed upgrade guidelines

N/A

Desired reviewers

@mention

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

[MarkEWaite]

The releases that are being updated have all been working well for me in my installation.

[MarkEWaite]

This PR is now ready for merge. We will merge it after approximately 24 hours if there is no negative feedback.