Yes, it looks like the resilience4j version that we are using is pretty out to date, BDK's client retry mechanic is building on resilience4j 1.7.1, and resilience4j changed the executeCheckSupplier method signature, this is the cause of your problem.
As you can see this BDK3.0.RC is not an official release, we'd like to see the feedback on the test both internally and externally, we will update the resilience4j dependency version in a next RC release.
Meanwhile, you unfortunately have to ...