Service binding doesn't work with Oracle and SqlServer

[xieshenzh]

Describe the bug

The kubernetes-service-binding extension injects database connection url with the format: jdbc:type://host:port/db.

But Oracle and SqlServer use different formats of connection url:
Oracle: jdbc:oracle:thin:@host:port/db
Vert.X Oracle client: oracle:thin:@host:port/db
SqlServer: jdbc:sqlserver://host:port;databaseName=db

As a result, the kubernetes-service-binding extension doesn't work when binding to Oracle or SqlServer.

---

Expected behavior

The kubernetes-service-binding extension injects correct database connection url when binding to Oracle and SqlServer.

Actual behavior

The kubernetes-service-binding extension injects database connection url which is incorrect when binding to Oracle and SqlServer.

How to Reproduce?

1. Create a simple quarkus application which connects to Oracle or SqlServer database. For example, use an application similar to the hibernate-orm-quickstart, and change the SQL client to be quarkus-jdbc-oracle, quarkus-jdbc-mssql or quarkus-reactive-oracle-client.
2. Add the kubernetes-service-binding extension to the project.
3. Run the Oracle or SqlServer service.
4. Follow the instructions to configure the binding for Oracle or SqlServer.
5. Build and run the quarkus application.

Output of uname -a or ver

No response

Output of java -version

No response

GraalVM version (if different from Java)

No response

Quarkus version or git rev

No response

Build tool (ie. output of mvnw --version or gradlew --version)

No response

Additional information

No response

[quarkus-bot]

/cc @Sgitario, @geoand, @iocanel