[BUG] MongoDB Atlas Chat Memory client closes and breaks flow

[jtguzman]

Describe the bug
When using the MongoDB Atlas Chat Memory, after some uses the client closes and it does not reconnect. This makes the flow to break with the message "Client must be connected before running operations"
The client reconects if the server is restarted, but after a random time it will close.

To Reproduce
Steps to reproduce the behavior:

1. Create a flow
2. Configure a new MongoDB Atlas Chat Memory node
3. Try the node successfully
4. Wait some time
5. Try again until it closes.

Expected behavior
The client should reconnect and the flow should continue without breaking.

Screenshots

Flow
Any flow with the node

Setup

• Installation docker-compose up -d
• Flowise Version 2.0.5
• OS: AWS Linux
• Browser: Edge

Additional context
A lot of problems with MongoDB and the 2.x.x update...

[HenryHengZJ]

Closing as #3469 merged