The auto-configured reactiveNeo4jTransactionManager may cause a failure due to multiple TransactionManager beans

[wilkinsona]

Forward port of issue #40895 to 3.3.x.

[yangyaofei]

please see this issue spring-projects/spring-data-neo4j#2931

the transactionManager in neo4j Neo4jDataAutoConfiguration.java will not create when using spring-data-jpa because in JpaBaseConfiguration the transactionManager for jpa will be created and then pop out error in neo4j show in issue below.

If I create a transactionManager for neo4j, the jpa will throw error when using like saveAndFlush.

I think (may not right or elegant) maybe disable Neo4jTransactionManager bean and make it in Neo4jTemplate bean is a way, or warp Neo4jTransactionManager into some container to prevent it extend from TransactionManager.