Feat/aerospike integration

[rohitpandit0007]

No description provided.

[linux-foundation-easycla]

• ❌ - login: @rohitpandit0007 / name: rohitpandit . The commit (1e50060, 3c7adf0, 46bc7af, 5c14926, 6fea98c, 7bbaf27, a0b69a8, a736bfa, d0012cb) is not authorized under a signed CLA. Please click here to be authorized. For further assistance with EasyCLA, please submit a support request ticket.
• ❌ - login: @rohitpandit0007 / name: rohitpandit0007 . The commit (2006b73, 3c7a962, c7fc6ba) is not authorized under a signed CLA. Please click here to be authorized. For further assistance with EasyCLA, please submit a support request ticket.
• ❌ - login: @venkata-manohar / name: venkata-manohar . The commit (2ccd376, 33a0ac1, 5b20635, f90c851) is not authorized under a signed CLA. Please click here to be authorized. For further assistance with EasyCLA, please submit a support request ticket.

[otelbot-java-instrumentation]

❌ The result from spotlessApply could not be committed to the PR branch, see logs: https://github.com/open-telemetry/opentelemetry-java-instrumentation/actions/runs/18522835911.

[otelbot-java-instrumentation]

❌ The result from generateLicenseReport could not be committed to the PR branch, see logs: https://github.com/open-telemetry/opentelemetry-java-instrumentation/actions/runs/18523062193.

[otelbot-java-instrumentation]

❌ The result from spotlessApply could not be committed to the PR branch, see logs: https://github.com/open-telemetry/opentelemetry-java-instrumentation/actions/runs/18523084738.

[otelbot-java-instrumentation]

❌ The result from generateLicenseReport could not be committed to the PR branch, see logs: https://github.com/open-telemetry/opentelemetry-java-instrumentation/actions/runs/18528880540.

[otelbot-java-instrumentation]

❌ The result from spotlessApply could not be committed to the PR branch, see logs: https://github.com/open-telemetry/opentelemetry-java-instrumentation/actions/runs/18528898232.

[SylvainJuge]

Hi @rohitpandit0007 , this PR is too large for us to properly being able to review it.

I would suggest to split changes in smaller and more manageable parts:

• adding instrumentation/vertx-aerospike-client-3.9 in this PR
• other necesary changes in separate PRs, for example all the other changes in instrumentation/vertx-*

I'm not familiar at all with aerospike and how it integrates into the vertx ecosystem, but with such large code changes it's better to split into multiple parts, ideally described into a single issue/sub-issues for more clarity on the progress and the overall motivation of this change.