Deprecate Service Binding module

Relates to: quarkusio#45916

docs/src/main/asciidoc/deploying-to-kubernetes.adoc

@@ -1555,6 +1555,8 @@ And this config map resource will be integrated into the generated `kubernetes.j
 
 == Service Binding [[service_binding]]
 
+WARNING: Service Binding support has been deprecated
+
 Quarkus supports the link:https://github.com/servicebinding/spec[Service Binding Specification for Kubernetes] to bind services to applications.
 
 Specifically, Quarkus implements the link:https://github.com/servicebinding/spec#workload-projection[Workload Projection] part of the specification, therefore allowing applications to bind to services, such as a Database or a Broker, without the need for user configuration.
@@ -1600,6 +1602,8 @@ For an example of a workload projection where the directory structure is include
 
 == Introduction to the Service Binding Operator
 
+WARNING: Service Binding support has been deprecated
+
 The link:https://github.com/redhat-developer/service-binding-operator[Service Binding Operator] is an Operator that implements link:https://github.com/servicebinding/spec[Service Binding Specification for Kubernetes] and is meant to simplify the binding of services to an application. Containerized applications that support link:https://github.com/servicebinding/spec#workload-projection[Workload Projection] obtain service binding information in the form of volume mounts. The Service Binding Operator reads binding service information and mounts it to the application containers that need it.
 
 The correlation between application and bound services is expressed through the `ServiceBinding` resources, which declares the intent of what services are meant to be bound to what application.

docs/src/main/asciidoc/kafka.adoc

@@ -2519,6 +2519,8 @@ include::kafka-dev-ui.adoc[leveloffset=+1]
 
 == Kubernetes Service Bindings
 
+WARNING: Service Binding support has been deprecated
+
 Quarkus Kafka extension supports
 xref:deploying-to-kubernetes.adoc[Service Binding Specification for Kubernetes].
 You can enable this by adding the `quarkus-kubernetes-service-binding` extension to your application.

extensions/kubernetes-service-binding/deployment/src/main/java/io/quarkus/kubernetes/service/binding/deployment/KubernetesServiceBindingConfig.java

@@ -10,6 +10,7 @@
 
 @ConfigMapping(prefix = "quarkus.kubernetes-service-binding")
 @ConfigRoot(phase = ConfigPhase.BUILD_TIME)
+@Deprecated(forRemoval = true, since = "3.19")
 public interface KubernetesServiceBindingConfig {
 
     /**

extensions/kubernetes-service-binding/runtime/src/main/java/io/quarkus/kubernetes/service/binding/runtime/KubernetesServiceBindingConfig.java

@@ -9,6 +9,7 @@
 
 @ConfigMapping(prefix = "quarkus.kubernetes-service-binding")
 @ConfigRoot(phase = ConfigPhase.RUN_TIME)
+@Deprecated(forRemoval = true, since = "3.19")
 public interface KubernetesServiceBindingConfig {
 
     /**

extensions/kubernetes-service-binding/runtime/src/main/resources/META-INF/quarkus-extension.yaml

@@ -6,4 +6,4 @@ metadata:
   - "kubernetes-service-binding"
   categories:
   - "cloud"
-  status: "preview"
+  status: "deprecated"

extensions/kubernetes-service-binding/spi/src/main/java/io/quarkus/kubernetes/service/binding/spi/ServiceBindingQualifierBuildItem.java

@@ -7,6 +7,7 @@
  * The qualifier does not encapsulate the target service coordinates, but information that given the right context can be mapped
  * to coordinates.
  */
+@Deprecated(forRemoval = true, since = "3.19")
 public final class ServiceBindingQualifierBuildItem extends MultiBuildItem {
 
     private final String id;

extensions/kubernetes-service-binding/spi/src/main/java/io/quarkus/kubernetes/service/binding/spi/ServiceBindingRequirementBuildItem.java

@@ -5,6 +5,7 @@
 /**
  * Build item that describes a kubernetes resource that the application needs to bind to.
  */
+@Deprecated(forRemoval = true, since = "3.19")
 public final class ServiceBindingRequirementBuildItem extends MultiBuildItem {
 
     private final String binding;