Override the outdated managed dependency on asm in guice-parent

[basil]

Amends #9182 to reduce our exposure to jenkinsci/plugin-pom#1032. Today, jenkins-bom is delivering a managed dependency on asm 9.5, coming from Guice. While it is bad that we deliver any reference to ASM from jenkins-bom, it is even worse that we deliver an old one. This overrides the old version to a more recent one, which is a strict improvement over the status quo. It is not a complete long-term solution to the problem, but it will surely not make things any worse than they are today, and will make them better in some cases.

Testing done

jenkinsci/workflow-job-plugin#471 exhibits the problem before this PR and passes after this PR.

Deployment plan

I plan to backport this to 2.479.1 LTS. Until that is generally available, I will re-introduce a workaround in plugin-pom (effectively reverting jenkinsci/plugin-pom#918 for a few weeks).

Proposed changelog entries

Developer: Prevent an old version of ASM from appearing as a managed dependency in plugin builds.

Proposed upgrade guidelines

N/A

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

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

[jonesbusy]

For reference : google/guice#1822

[jglick]

(until we can get rid of Guice which should never have been added to Jenkins to begin with)

[MarkEWaite]

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