Fixing JakartaInitServiceNameInstrumentation

[eyalkoren]

Fixes #2545 - a small bug introduced through #2418

[ghost]

💚 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-03-29T08:55:08.191+0000

• Duration: 50 min 36 sec

Test stats 🧪

Test	Results
Failed	0
Passed	2840
Skipped	20
Total	2860

💚 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!)

[SylvainJuge]

LGTM, we should probably take the time to see why it wasn't properly tested.

[eyalkoren]

we should probably take the time to see why it wasn't properly tested

This instrumentation should not be affected on javax-based Servlet containers, only the jakarta ones, but I think we do have such being tested, which means there is no test for this specific functionality.