fix: grizzly client reverse muzzle check

[ygree]

What Does This Do

Widen Grizzly client muzzle range because Grizzly 5 still exposes the com.ning AHC API and the old 1.16 cap causes a false inverse muzzle failure

Motivation

Broken CI

Additional Notes

:dd-java-agent:instrumentation:grizzly:grizzly-client-1.9:muzzle-AssertFail-org.glassfish.grizzly-grizzly-http-client-5.0.0 FAILED

Ref: #11256

Contributor Checklist

• Format the title according to the contribution guidelines
• Assign the type: and (comp: or inst:) labels in addition to any other useful labels
• Avoid using close, fix, or any linking keywords when referencing an issue
  Use solves instead, and assign the PR milestone to the issue
• Update the CODEOWNERS file on source file addition, migration, or deletion
• Update public documentation with any new configuration flags or behaviors

Jira ticket: [PROJ-IDENT]

Note: Once your PR is ready to merge, add it to the merge queue by commenting /merge. /merge -c cancels the queue request. /merge -f --reason "reason" skips all merge queue checks; please use this judiciously, as some checks do not run at the PR-level. For more information, see this doc.

[github-actions]

Hi! 👋 Thanks for your pull request! 🎉

To help us review it, please make sure to:

• Add at least one type, and one component or instrumentation label to the pull request

If you need help, please check our contributing guidelines.

[mcculls]

Approving to get master unblocked - using a range of "[1.9,1.16],[5,6)" should also work and is more accurate

[dd-octo-sts]

/merge

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-05-02 00:14:06 UTC ℹ️ Start processing command /merge

---

2026-05-02 00:14:12 UTC ℹ️ MergeQueue: pull request added to the queue

The expected merge time in master is approximately 1h (p90).

---

2026-05-02 01:42:30 UTC ℹ️ MergeQueue: This merge request was merged