Suppress SE_INNER_CLASS SpotBugs violations

[basil]

Suppresses the following two SpotBugs violations:

[ERROR] Medium: hudson.util.ProcessTree$Remote$RemoteProcess is serializable and an inner class [hudson.util.ProcessTree$Remote$RemoteProcess] At ProcessTree.java:[lines 2180-2225] SE_INNER_CLASS
[ERROR] Medium: hudson.util.ProcessTree$SerializedProcess is serializable and an inner class [hudson.util.ProcessTree$SerializedProcess] At ProcessTree.java:[lines 397-406] SE_INNER_CLASS

The description of the check indicates that it's meant to catch accidental serializations of the outer instance, which might serialize more data than intended. In this case, the comments and the code are very clear that serializing the outer instance is intentional: we do so because it contains the process tree against which we call get() in the serialized inner instance. Since this code is working as intended, there is nothing to do except suppress the warning.

Proposed changelog entries

N/A

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

[basil]

This PR is now ready for merge. We will merge it after approximately 24 hours if there is no negative feedback. Please see the merge process documentation for more information about the merge process. Thanks!