PYTHON-6149 Fix condition for minPoolSize validation

[MaddipatlaChetan24]

PYTHON-6149

Changes in this PR

• _parse_pool_options only exempted maxPoolSize=None from the minPoolSize <= maxPoolSize check. The docs say both 0 and None mean no limit, and the pool treats both as unlimited. This made MongoClient(maxPoolSize=0, minPoolSize=5) raise ValueError while maxPoolSize=None was accepted.
• The check now skips both 0 and None.

Test Plan

• Manual check on PyMongo 4.18.2:
  • maxPoolSize=0 and maxPoolSize=None, each with minPoolSize=5: accepted.
  • maxPoolSize=10, minPoolSize=20, and minPoolSize=200 against the default max of 100: still raise ValueError.
  • maxPoolSize=10, minPoolSize=10: still accepted.

Checklist

Checklist for Author

• Did you update the changelog (if necessary)?
• Is the intention of the code captured in relevant tests?
• If there are new TODOs, has a related JIRA ticket been created?

Checklist for Reviewer

• Does the title of the PR reference a JIRA Ticket?
• Do you fully understand the implementation? (Would you be comfortable explaining how this code works to someone else?)
• Have you checked for spelling & grammar errors?
• Is all relevant documentation (README or docstring) updated?

[aclark4life]

Thanks @MaddipatlaChetan24 ! Can you please add a test and changelog entry?

[codecov]

Codecov Report

❌ Patch coverage is 0% with 1 line in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
pymongo/client_options.py	0.00%	0 Missing and 1 partial ⚠️

📢 Thoughts on this report? Let us know!

[codeowners-service-app]

Assigned caseyclements for team dbx-python because aclark4life is out of office.

[evergreen-ci-prod]

There is an existing patch(es) for this commit SHA:

• Evergreen patch with PR

Please note that the status that is posted is not in the context of this PR but rather the (latest) existing patch and that may affect some tests that may depend on the particular PR. If your tests do not rely on any PR-specific values (like base or head branch name) then your tests will report the same status. If you would like a patch to run in the context of this PR and abort the other(s), comment 'evergreen retry'.