When application is registered under the ROOT path (/), static content is not served anymore

I understand that this might not be an issue, since it's by design. As seen in the docs:
https://github.com/resteasy/resteasy-spring-boot/blob/master/mds/USAGE.md#jax-rs-application-registration-methods

But in this approach, if the application is registered under the ROOT path ("/") RESTEasy takes over all the handlers, and on SpringBoot static content just ain't be served any more.

In our particular scenario (Kogito) we don't know beforehand which path/context we will generate the REST resources (can be dozens), so we register in the ROOT path.

Is there any way to instead of returning 404, handle the request back to the chain so SpringBoot MVC will take care to serve the content (or return 404)? Ideally, RESTEasy could take care only on its registered Paths instead.