v3.3.2: Passes EntityManager to recalculateEntities in BaseListener

Ensures that the entity manager which triggered the event is used for recomputing entity change sets, rather than relying on an internal property.

v3.3.1: Adds optimistic locking to fetchField

Allows the fetchField method to use pessimistic write locking.

This ensures that data being fetched is locked during the process,
preventing concurrent modifications and potential data conflicts.

v3.3: Improves property change detection and adds locking.

Enhances the `isPropertyChanged` method to handle both single properties and arrays of properties, allowing for more flexible change detection.

Adds `getLock` and `releaseLock` methods to the EntityManager, enabling advisory locking for specific operations.

v3.2.7: Removes DQL part modification restrictions

Temporarily removes the restrictions on modifying 'select',
'distinct', and 'orderBy' DQL parts within filters. This
allows for greater flexibility in query customization,
potentially needed for specific use cases. The restrictions
may be re-evaluated and re-introduced later with a more
refined approach.

v3.2.6

Update composer.json

v3.2.5

Update composer.json

v3.2.4: Changes identifier visibility to protected

Updates the visibility of the identifier property to protected, allowing subclasses to access and utilize it.
This promotes code reusability and avoids direct access from outside the class hierarchy.

v3.2.3: Adds Entity::isNew() method

Adds the `isNew()` method to the `Entity` interface.

This method allows to determine whether an entity
has already been persisted or not.

v3.2.2: Removes BaseEntity and moves isNew() to Identifier trait

Removes the BaseEntity class as it was redundant.

Moves the isNew() method to the Identifier trait, as it's directly related to the identifier logic and provides a more consistent and encapsulated approach for checking entity freshness.

v3.2.1: Marks BaseEntity as a MappedSuperclass

Marks the `BaseEntity` as a Doctrine `MappedSuperclass`.

This change allows other entities to inherit from it
without `BaseEntity` being managed as a standalone entity
in the database.