Optimize entity deletion in SimpleJpaRepository

[Seol-JY]

Optimize the delete method in SimpleJpaRepository to improve performance in certain scenarios. The main change is to first check if the entity is already managed by the EntityManager.

• Reordered the deletion logic to prioritize managed entities
• Added a check for entityManager.contains(entity) at the beginning of the method

The goal of this change is to reduce unnecessary database lookups when deleting managed entities, potentially improving performance in high-throughput scenarios.

The goal of this change is to optimize the deletion process for entities that are already managed by the EntityManager (present in the first-level cache). This can potentially improve performance in scenarios where entities are likely to be in the cache before deletion, such as when using the deleteById method after recent read or write operations.

Please point out any potential risks or edge cases where this change might lead to unexpected behavior.

[quaff]

The goal of this change is to reduce unnecessary database lookups when deleting managed entities

entityManager.find(type, entityInformation.getId(entity)) will not trigger database lookup If entityManager.contains(entity).

[mp911de]

Thank you for your contribution. That's merged, polished, and backported now.