fix(spring): make dapr-spring-boot-observation non-optional in autoconfigure poms

The autoconfigure classes directly reference ObservationDaprClient and
ObservationDaprWorkflowClient in their bean factory methods. When the
observation module was marked <optional>, it was not propagated through
the starters, causing a potential NoClassDefFoundError at runtime for
users with a non-noop ObservationRegistry (e.g. actuator + tracing).

Removing <optional> restores the original behavior: the Observation
decorator classes are always on the classpath wherever the autoconfig
is loaded.

Signed-off-by: Javier Aliaga <javier@diagrid.io>

Author: javier-aliaga

dapr-spring/dapr-spring-boot-4-autoconfigure/pom.xml

@@ -92,7 +92,6 @@
     <dependency>
       <groupId>io.dapr.spring</groupId>
       <artifactId>dapr-spring-boot-observation</artifactId>
-      <optional>true</optional>
     </dependency>
     <dependency>
       <groupId>io.micrometer</groupId>

dapr-spring/dapr-spring-boot-autoconfigure/pom.xml

@@ -61,7 +61,6 @@
     <dependency>
       <groupId>io.dapr.spring</groupId>
       <artifactId>dapr-spring-boot-observation</artifactId>
-      <optional>true</optional>
     </dependency>
     <dependency>
       <groupId>io.micrometer</groupId>