Use non-shared netty dependency for Spring Boot integration

## Expected Behavior

Users should be able to use native compilation (with GraalVM) for applications using the Dapr Java Spring Boot integration.

## Actual Behavior

The netty-shaded library doesn't work with native compilation.

## Steps to Reproduce the Problem

Create a Spring Boot application, add the Spring Boot Dapr integration and try to compile a native image:

```

io.dapr.spring
dapr-spring-boot-starter
${dapr-java-sdk.alpha-version}

```

## Workaround

```

io.dapr.spring
dapr-spring-boot-starter
${dapr-java-sdk.alpha-version}


io.grpc
grpc-netty-shaded

io.grpc
grpc-netty
${grpc.version}

```

You need to make sure that `${grpc.version}` matches with the one included by the Java Dapr SDK.

@artursouza can you give me some background about why we need the shaded version? Do you have anything against using the non-shaded version when integrating with Spring Boot?

## Release Note

RELEASE NOTE:

Inizia dalla dichiarazione della dipendenza dapr-spring-boot-starter e verifica come grpc-netty-shaded viene incluso nell’integrazione Spring Boot. Confronta il workaround per grpc-netty non shaded descritto nell’issue, quindi verifica che un’applicazione Spring Boot che utilizza lo starter possa compilare un GraalVM native image senza esclusioni di dipendenze.

Scritto dal modello di indicizzazione a partire dal testo della issue.