Remove Oracle JDBC driver out of the box

[abstractj]

Description

As Keycloak seeks to complete the incubating onboarding items, it must align with the CNCF license policy, which mandates board approval for non-Apache 2.0 dependencies.

To resolve potential license compliance issues, modify future Keycloak community releases to exclude the Oracle driver, requiring it to be installed separately by users. This practice helps address licensing concerns. Note that this change is not applicable to past releases.

Acceptance Criteria

1. Confirm that excluding the Oracle driver from future releases addresses specific licensing violations.
2. Update installation guides to include instructions for users on how to install the Oracle driver manually.
3. Adjust the build process to exclude the Oracle driver from all future community releases.
4. Communicate this change to the community, highlighting the reasons related to licensing compliance.

[abstractj]

@keycloak/core-clients @keycloak/core-iam could you please triage and add to your team's backlog?

cc @keycloak/maintainers

[ahus1]

This might be an @keycloak/cloud-native issue as it relates to Quarkus and has already been implemented for downstream. The instructions on how to install the Oracle driver if it hasn't been included in the dist already exist for downstream:

keycloak/docs/guides/server/db.adoc

Lines 41 to 75 in 9db1443

	=== Installing the Oracle Database driver
	To install the Oracle Database driver for {project_name}:
	. Download the `ojdbc11` and `orai18n` JAR files from one of the following sources:
	.. *Zipped JDBC driver and Companion Jars* version ${properties["oracle-jdbc.version"]} from the https://www.oracle.com/database/technologies/appdev/jdbc-downloads.html[Oracle driver download page].
	.. Maven Central via `link:++https://repo1.maven.org/maven2/com/oracle/database/jdbc/ojdbc11/${properties["oracle-jdbc.version"]}/ojdbc11-${properties["oracle-jdbc.version"]}.jar++[ojdbc11]` and `link:++https://repo1.maven.org/maven2/com/oracle/database/nls/orai18n/${properties["oracle-jdbc.version"]}/orai18n-${properties["oracle-jdbc.version"]}.jar++[orai18n]`.
	.. Installation media recommended by the database vendor for the specific database in use.
	. When running the unzipped distribution: Place the `ojdbc11` and `orai18n` JAR files in {project_name}'s `providers` folder
	. When running containers: Build a custom {project_name} image and add the JARs in the `providers` folder. When building a custom image for the Operator, those images need to be optimized images with all build-time options of {project_name} set.
	+
	A minimal Dockerfile to build an image which can be used with the {project_name} Operator and includes Oracle Database JDBC drivers downloaded from Maven Central looks like the following:
	+
	[source,dockerfile,subs="attributes+"]
	----
	FROM quay.io/keycloak/keycloak:{containerlabel}
	ADD --chown=keycloak:keycloak https://repo1.maven.org/maven2/com/oracle/database/jdbc/ojdbc11/${properties["oracle-jdbc.version"]}/ojdbc11-${properties["oracle-jdbc.version"]}.jar /opt/keycloak/providers/ojdbc11.jar
	ADD --chown=keycloak:keycloak https://repo1.maven.org/maven2/com/oracle/database/nls/orai18n/${properties["oracle-jdbc.version"]}/orai18n-${properties["oracle-jdbc.version"]}.jar /opt/keycloak/providers/orai18n.jar
	# Setting the build parameter for the database:
	ENV KC_DB=oracle
	# Add all other build parameters needed, for example enable health and metrics:
	ENV KC_HEALTH_ENABLED=true
	ENV KC_METRICS_ENABLED=true
	# To be able to use the image with the {project_name} Operator, it needs to be optimized, which requires {project_name}'s build step:
	RUN /opt/keycloak/bin/kc.sh build
	----
	+
	See the <@links.server id="containers" /> {section} for details on how to build optimized images.
	Then continue configuring the database as described in the next section.

[vmuzikar]

Yes, this would be done by the Cloud Native team. We'll look into it.

[vmuzikar]

Based on an offline discussion with @abstractj, changed the milestone and priority.