Add failing tests to reproduce POOL-413

[rajucomp]

Thanks for your contribution to Apache Commons! Your help is appreciated!

Before you push a pull request, review this list:

• Read the contribution guidelines for this project.
• Read the ASF Generative Tooling Guidance if you use Artificial Intelligence (AI).
• I used AI to create any part of, or all of, this pull request. Which AI tool was used to create this pull request, and to what extent did it contribute?
• Run a successful build using the default Maven goal with mvn; that's mvn on the command line by itself.
• Write unit tests that match behavioral changes, where the tests fail if the changes to the runtime are not applied. This may not always be possible, but it is a best practice.
• Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
• Each commit in the pull request should have a meaningful subject line and body. Note that a maintainer may squash commits during the merge process.

In a GenericObjectPool it is possible to configure a maximum number of idle objects to be kept by the pool while they are not in use.

In unfortunate circumstances, if several threads return an object to the pool at the same time, the check on the maximum number of idle objects may be dismissed. This results in the pool keeping more idle objects than configured.

Looking into the source code of the returnObject method of the GenericObjectPool, it seems that there is no synchronization between the moment the check is made for the maxIdle configuration and the moment the object is destroyed:

final int maxIdleSave = getMaxIdle();
if (isClosed() || maxIdleSave > -1 && maxIdleSave <= idleObjects.size()) {
    try {
        destroy(p, DestroyMode.NORMAL);
    } catch (final Exception e) {
        swallowException(e);
    }
    try {
        ensureIdle(1, false);
    } catch (final Exception e) {
        swallowException(e);
    }
}

The PR contains the test to demonstrate the failure. A fix is ready for the same. Once the maintainer confirm the bug, a seperate PR for the fix will be raised.

[rajucomp]

@garydgregory Could you run the pipelines please ? I have added some comments on the JIRA about the fix. Would appreciate your feedback. Thanks@