[9.1] (backport #17766) Fix deprecation warning with latest jruby/bundler

[mergify]

Release notes

[rn:skip]

What does this PR do?

This commit updates the pluginmanager to not use a deprecated argument.

See rubygems/rubygems@d1963bf

Why is it important/What is the impact to the user?

Without this patch use of the plugin manager can surface warnings that are not actionable by the logstash user. This commit fixes the underlying issue so messages are no longer surfaced.

Checklist

• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have made corresponding change to the default configuration files (and/or docker env variables)
• I have added tests that prove my fix is effective or that my feature works

Related issues

• Manual testing for Jruby 9.4.13.0 #17732

Logs

bash-5.1$ logstash-plugin install file:///usr/share/logstash/logstash-offline-plugins-9.1.0.zip
Using bundled JDK: /usr/share/logstash/jdk
Installing file: /usr/share/logstash/logstash-offline-plugins-9.1.0.zip
[DEPRECATED] `Definition#lock` was passed a target file argument. To fix this warning, remove it from the `Definition#lock` call.
Resolving dependencies...
Install successful

---

This is an automatic backport of pull request #17766 done by [Mergify](https://mergify.com).

[github-actions]

🤖 GitHub comments

Expand to view the GitHub comments

Just comment with:

• run docs-build : Re-trigger the docs validation. (use unformatted text in the comment!)

[elastic-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarQube

[elasticmachine]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: bd4b11b

Failed CI Steps

• 🥼 Integration Tests / part 2-of-3
• 🥼 Integration Tests / part 2-of-3

cc @donoghuc