Error when AutoFactory implementing methods cannot match create()

[tanvir-ux]

Summary

• When an @AutoFactory(implementing = …) (or extending) abstract method has no matching factory create overload, AutoFactory used to emit a forwarding stub return create(args).
• If that abstract method was itself named create, the stub called itself and threw StackOverflowError at runtime. The usual trigger is forgetting @Provided on a constructor parameter, which silently turns that parameter into an extra factory argument (fixes AutoFactory: missing @Provided leads to StackOverflowError #697).
• The processor now reports a compile-time error that names the unmatched method and points at @Provided, instead of generating the recursive stub.

Test plan

• mvn test in factory/ — AutoFactoryProcessorTest 185 tests (7 skipped), AutoFactoryProcessorNegativeTest including new missingProvidedLeadsToUnmatchedInterfaceMethod
• mvn verify in factory/ — unit tests + invoker ITs passed
• Reviewer: compile the AutoFactory: missing @Provided leads to StackOverflowError #697 sample (@AutoFactory(implementing = Factory.class) with a missing @Provided) and confirm a clear error on @AutoFactory rather than a runtime StackOverflowError