Add support for Jedis 4

[eyalkoren]

What does this PR do?

Closes #2616

The proposed instrumentation hereby seems simpler and is more suitable for easily supporting Jedis 4 as well.
All existing tests pass, so I can't say if I missed anything with this simplification.

Checklist

• This is a new plugin
  • I have updated CHANGELOG.asciidoc - add also as a refactoring change for older Jedis versions
  • My code follows the style guidelines of this project
  • I have made corresponding changes to the documentation
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • I have updated supported-technologies.asciidoc
  • Added an API method or config option? Document in which version this will be introduced
  • Added an instrumentation plugin? Describe how you made sure that old, non-supported versions are not instrumented by accident - the old versions instrumentation is disabled for Jedis 4 based on class loader matching and the new one is specifically enabled for Jedis 4 similarly

[apmmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2022-05-16T12:21:19.131+0000

• Duration: 48 min 51 sec

Test stats 🧪

Test	Results
Failed	0
Passed	2872
Skipped	22
Total	2894

💚 Flaky test report

Tests succeeded.

🤖 GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

• run benchmark tests : Run the benchmark tests.

• run jdk compatibility tests : Run the JDK Compatibility tests.

• run integration tests : Run the Agent Integration tests.

• run end-to-end tests : Run the APM-ITs.

• run windows tests : Build & tests on windows.

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

[felixbarny]

LGTM, I like the simpler approach of instrumenting just one entry point instead of all the command method implementations!