[JENKINS-65442] - Improve performance when encoding unicode characters in JSON API + Remove Stapler's Guava dependency

[basil]

See JENKINS-65442. This PR updates Stapler to the latest version, which includes the fix for JENKINS-65442 and jenkinsci/stapler#220 (which removes Stapler's dependency on Guava).

Proposed changelog entries

• rfe, JENKINS-65442 - Improve performance when encoding unicode characters in JSON API
  • Stapler 1527.ve41b3ce15c05 changelog: https://github.com/stapler/stapler/releases/tag/1527.ve41b3ce15c05
• internal - Remove dependency on Guava in Stapler
  • Stapler 1527.ve41b3ce15c05 changelog: https://github.com/stapler/stapler/releases/tag/1527.ve41b3ce15c05
  • Stapler 1532.vfcf95addcb5f changelog: https://github.com/stapler/stapler/releases/tag/1532.vfcf95addcb5f

Proposed upgrade guidelines

N/A

Submitter checklist

• (If applicable) Jira issue is well described
• Changelog entries and upgrade guidelines are appropriate for the audience affected by the change (users or developer, depending on the change). Examples
  • Fill-in the Proposed changelog entries section only if there are breaking changes or other changes which may require extra steps from users during the upgrade
• Appropriate autotests or explanation to why this change has no tests
• For dependency updates: links to external changelogs and, if possible, full diffs

Desired reviewers

@mention

Maintainer checklist

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

• There are at least 2 approvals for the pull request and no outstanding requests for change
• Conversations in the pull request are over OR it is explicit that a reviewer does not block the change
• Changelog entries in the PR title and/or Proposed changelog entries are correct
• Proper changelog labels are set so that the changelog can be generated automatically
• If the change needs additional upgrade steps from users, upgrade-guide-needed label is set and there is a Proposed upgrade guidelines section in the PR title. (example)
• 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).

[oleg-nenashev]

❤️

We may merge it in 24 hours if there is no negative feedback. Please see the merge process documentation for more information about the merge process

[oleg-nenashev]

We will need changelog, because it includes multiple other changes

[oleg-nenashev]

@basil please review the suggested changelog. It would be also great if you could keep the pull request template in your pull requests.

We may merge it in 24 hours if there is no negative feedback. Please see the merge process documentation for more information about the merge process

[basil]

Sorry! I normally do that, but I had repurposed this PR for something other than its original purpose and had forgotten to update the description. I just updated it now to conform to the template.