Closes gh-22941

See gh-22940

Closes gh-22652

The current arrangement with Neo4j does not allow us to know for sure
that the user intends to use `@Transactional` for reactive or imperative
operations.

The main reason for that is that the only trigger for the reactive
auto-configuration is the presence of reactor on the classpath given
that the Neo4j driver ships with both styles in the same jar. And
reactor can be on the classpath for a number of reasons that are
unrelated to imperative access (typically `WebClient`).

This commits removes the auto-configuration of the
ReactiveNeo4jAutoConfiguration and makes sure that if the user defines
one, the regular `PlatformTransactionManager` backs off. This is
a temporarily situation until we can provide a better signal that the
user intends to primarily use imperative repositories.

Closes gh-22940

Closes gh-22938

This reverts commit 6547ea56, reversing
changes made to e9e4a34e.

Fixes gh-22039

Closes gh-22937

Closes gh-22936

Closes gh-22935

Closes gh-22932

Closes gh-22892

Closes gh-22934

Closes gh-22931

Closes gh-22930

* pr/22919:
  Polish "Fix conditions that lead to auto-configure PushGateway"
  Fix conditions that lead to auto-configure PushGateway

Closes gh-22919

See gh-22919

See gh-22919

Closes gh-22920

Closes gh-22928

Closes gh-22921

See gh-22916

Closes gh-22923

Fixes gh-22916

* gh-22736:
  Polish "Add pullPolicy option for image building"
  Add pullPolicy option for image building

Closes gh-22736

See gh-22736

This commit adds a pullPolicy option to the configuration of the Maven
plugin spring-boot:build-image goal and the Gradle plugin bootBuildImage
task. The new option gives users control over pulling the builder image
and run image from a remote image registry to the local Docker daemon.

See gh-22736

Closes gh-22729

Closes gh-22843

Closes gh-22842

Closes gh-22730

* gh-22710:
  Introduce @ForkedClassPath for testing unmodified class path

Closes gh-22710

See gh-22710