Feat: add a configuration to control maximum exceptions can be collect when processing persistence

[LennonChin]

This PR adds a parameter to control the maximum number of exceptions that can be caught during persistence operations.

Currently, some operations in PersistenceManager and ExecutionContext iterate over the fields of the passed-in objects and capture all exceptions in an ArrayList. In certain scenarios (e.g., lost or disconnected database connections), the iteration process throws exceptions (the iterator's state is not updated due to the exception), and these exceptions are caught by the outer layer, causing the iteration to continue, potentially leading to an infinite loop. Furthermore, storing a large number of exceptions in the ArrayList can cause JVM memory usage to spike, potentially resulting in an OutOfMemoryError.

We've added a parameter datanucleus.persistence.maximumCollectNestedExceptions, which specifies the maximum number of exceptions that can be caught. The default value is Integer.MAX_VALUE, ensuring consistency with existing behavior. Users can configure this parameter, with a minimum value of 1. When the number of exceptions thrown during the iteration operation exceeds or equals this value, the iteration operation will be fast-failed quickly to avoid an infinite loop.

Also, please note that PR datanucleus/datanucleus-api-jdo#145 uses the newly added parameters.

Fixes #540

[LennonChin]

Gently ping @andyjefferson please review this PR.