In a Spring Boot application, a @Transactional method is called from another method within the same bean (self-invocation). Even with CGLIB proxying enabled, the transaction is not applied. How does Spring’s proxy-based AOP implementation cause this behavior internally, and what design choices in the framework prevent transaction interception in this case?