feat: migrate vertx 4 to 5

[Sunil-SKS]

The Future implementation has been removed from PendingDeployment to support the migration from Vert.x 4 to
Vert.x 5. The PendingDeployment class now returns objects directly, rather than Futures.

Migration document
https://vertx.io/docs/guides/vertx-5-migration-guide

• Vertx used v 5.0.7
• logback-classic - 1.5.19
• commons-io:commons-io - 2.14.0
• vertx-launcher-legacy-cli - 5.0.7
• micrometer-registry-prometheus - 1.15.8

[cla-assistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 2 committers have signed the CLA.

✅ Sunil-SKS
❌ halber
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[Sunil-SKS]

Hello Team,

FYI

• The code is moved to migration, hence this pull request can be closed
  [https://github.com/feat: remove future implementation from the pendingdeployment class #679]

  The Future implementation has been removed from PendingDeployment to support the migration from Vert.x 4 to
  Vert.x 5. The PendingDeployment class now returns objects directly, rather than Futures.

• Migration document
  [https://vertx.io/docs/guides/vertx-5-migration-guide]

Please review the pull request

[sonarqubecloud]

Quality Gate passed

Issues
11 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud