Using custom header in REST client together with `@NotBody` annotated argument results in warning from EndpointIndexer about quarkus

[quarkus-bot]

/cc @cescoffier (rest-client), @geoand (rest-client)

[mzuber]

@geoand The fix you added in #38800 was released as part of Quarkus 3.7.4 but I'm still seeing the same warnings:

2024-02-23 14:51:50,031 WARN  [org.jbo.res.rea.com.pro.EndpointIndexer] (build-105) Using a body parameter with jakarta.ws.rs.GET is strongly discouraged. Offending method is 'com.example.MyTestClient#java.lang.String getSomethingById(java.lang.String id, java.lang.String token)'
2024-02-23 14:52:00,934 INFO  [io.quarkus] (Quarkus Main Thread) example-app 1.0.0 on JVM (powered by Quarkus 3.7.4) started in 14.306s. Listening on: http://localhost:12000
2024-02-23 14:52:00,935 INFO  [io.quarkus] (Quarkus Main Thread) Profile dev activated. Live Coding activated.
2024-02-23 14:52:00,935 INFO  [io.quarkus] (Quarkus Main Thread) Installed features: [agroal, cache, cdi, hibernate-orm, hibernate-orm-panache, hibernate-validator, jdbc-postgresql, liquibase, micrometer, narayana-jta, reactive-routes, rest-client-reactive, rest-client-reactive-jackson, resteasy-reactive, resteasy-reactive-jackson, security, smallrye-context-propagation, smallrye-graphql, smallrye-health, smallrye-openapi, smallrye-reactive-messaging, smallrye-reactive-messaging-amqp, swagger-ui, vertx]

Am I missing anything here?

[geoand]

You are right, I see the warning is still there, so I'll have to reopen