Camel bean not working with 3.0 for external libraries

I have a custom library that uses jandex to expose Quarkus Beans that are ApplicationScoped. Previous to Quarkus Camel 3.0 I could do the following and it worked with no problem.

```
from("direct:doSomething")
.bean(MyBean.class,"cleanup")
.end();
```

In 3.0, I am getting the following exception, Failed to create route...because No bean could be found in the registry for: myBean. Not sure how to address this.

Start by reproducing the Camel 3.0 route using the external Jandex-based library and the shown .bean(MyBean.class, "cleanup") call. Trace how the ApplicationScoped MyBean is exposed to the registry and compare that with the earlier behavior; done means the route starts and invokes cleanup without the missing-bean exception.

Written by the indexing model from the issue text.