Remove EntityInformation customization from Entity State Detection Strategies.

Customizing EntityInformation has only a single use-case within JPA. All other modules should use customization using the mentioned mechanisms as the underlying MappingContext handles typically IsNew detection but customizing the MappingContext (PersistentEntity) is a deeply involved task.

Closes #3364

Author: mp911de

src/main/antora/modules/ROOT/pages/is-new-state-detection.adoc

@@ -23,8 +23,4 @@ See the {spring-data-commons-javadoc-base}/org/springframework/data/domain/Persi
 _Note: Properties of `Persistable` will get detected and persisted if you use `AccessType.PROPERTY`.
 To avoid that, use `@Transient`._
 
-|Providing a custom `EntityInformation` implementation
-|You can customize the `EntityInformation` abstraction used in the repository base implementation by creating a subclass of the module specific repository factory and overriding the `getEntityInformation(…)` method.
-You then have to register the custom implementation of module specific repository factory as a Spring bean.
-Note that this should rarely be necessary.
 |===