refactor: replaces custom MongoDBProxy implementation with PyMongo's built-in retry functionality

[wgu-ram-chandra]

Description

This PR removes the usage of the custom mongodb_proxy package from edx-platform, replacing it with MongoDB's built-in retry functionality via retryReads=True.

Changes made:

• Removed all references to mongodb_proxy.MongoProxy from connection logic.
• Updated connect_to_mongodb() to always use retryReads=True.
• Uninstalled openedx-mongodbproxy from edx-platform requirements.
• Manually smoke-tested LMS and Studio, both function normally without mongodb_proxy.

Built-in vs previous behavior:

• The current @autoretry_read logic retried AutoReconnect up to 5 times with delay.
• retryReads=True provides a single automatic retry for transient errors like AutoReconnect, NotPrimaryError, etc

In Current `@autoretry_read` Implementation	Built-in `retryReads`(documentation)

Proposed Solution

Is a single automatic retry (retryReads=True) sufficient for our use case?

If not, we can add a lightweight wrapper at the call site where additional retries are needed. For example:

def retry_on_autoreconnect(fn, tries=5, wait=0.1):
    for attempt in range(tries):
        try:
            return fn()
        except AutoReconnect:
            if attempt == tries - 1:
                raise
            time.sleep(wait)

# Sample usage
return retry_on_autoreconnect(lambda: collection.find(...))

References

• https://pymongo.readthedocs.io/en/stable/api/pymongo/mongo_client.html
• https://github.com/openedx/MongoDBProxy/blob/master/mongodb_proxy.py

Fixes: #35210

CC: @kdmccormick

[openedx-webhooks]

Thanks for the pull request, @wgu-ram-chandra!

This repository is currently maintained by @openedx/wg-maintenance-edx-platform.

Once you've gone through the following steps feel free to tag them in a comment and let them know that your changes are ready for engineering review.

🔘 Get product approval

If you haven't already, check this list to see if your contribution needs to go through the product review process.

• If it does, you'll need to submit a product proposal for your contribution, and have it reviewed by the Product Working Group.
  • This process (including the steps you'll need to take) is documented here.
• If it doesn't, simply proceed with the next step.

🔘 Provide context

To help your reviewers and other members of the community understand the purpose and larger context of your changes, feel free to add as much of the following information to the PR description as you can:

• Dependencies

  This PR must be merged before / after / at the same time as ...

• Blockers

  This PR is waiting for OEP-1234 to be accepted.

• Timeline information

  This PR must be merged by XX date because ...

• Partner information

  This is for a course on edx.org.

• Supporting documentation
• Relevant Open edX discussion forum threads

🔘 Get a green build

If one or more checks are failing, continue working on your changes until this is no longer the case and your build turns green.

Details

---

Where can I find more information?

If you'd like to get more details on all aspects of the review process for open source pull requests (OSPRs), check out the following resources:

• Overview of Review Process for Community Contributions
• Pull Request Status Guide
• Making changes to your pull request

When can I expect my changes to be merged?

Our goal is to get community contributions seen and reviewed as efficiently as possible.

However, the amount of time that it takes to review and merge a PR can vary significantly based on factors such as:

• The size and impact of the changes that it introduces
• The need for product review
• Maintenance status of the parent repository

💡 As a result it may take up to several weeks or months to complete a review and merge your PR.

[dwong2708]

I suggest testing it in a sandbox environment with some sample courses and components and the second commit looks like duplicated

[open-craft-grove]

Sandbox deployment failed 💥
Please check the settings and requirements.
Retry deployment by pushing a new commit or updating the requirements/settings in the pull request's description.
📜 Failure Logs
ℹ️ Grove Config, Tutor Config, Tutor Requirements

[open-craft-grove]

Sandbox deployment failed 💥
Please check the settings and requirements.
Retry deployment by pushing a new commit or updating the requirements/settings in the pull request's description.
📜 Failure Logs
ℹ️ Grove Config, Tutor Config, Tutor Requirements

[open-craft-grove]

Sandbox deployment failed 💥
Please check the settings and requirements.
Retry deployment by pushing a new commit or updating the requirements/settings in the pull request's description.
📜 Failure Logs
ℹ️ Grove Config, Tutor Config, Tutor Requirements

[open-craft-grove]

Sandbox deployment successful 🚀
🎓 LMS
📝 Studio
ℹ️ Grove Config, Tutor Config, Tutor Requirements

[wgu-ram-chandra]

@dwong2708 I was able to successfully test course creation in the sandbox, thank you!

[open-craft-grove]

Sandbox deployment failed 💥
Please check the settings and requirements.
Retry deployment by pushing a new commit or updating the requirements/settings in the pull request's description.
📜 Failure Logs
ℹ️ Grove Config, Tutor Config, Tutor Requirements

[kdmccormick]

Looks great, thanks Ram! I'll merge later today.

[wgu-ram-chandra]

Thanks Kyle!

[edx-pipeline-bot]

2U Release Notice: This PR has been deployed to the edX staging environment in preparation for a release to production.

[edx-pipeline-bot]

2U Release Notice: This PR has been deployed to the edX production environment.

[edx-pipeline-bot]

2U Release Notice: This PR has been deployed to the edX production environment.