Handle expired resumeTokens

[BartekGravity]

Handle cases, where the resumeToken is expired (usually expires after 48 hours and is deleted from opLog in MongoDB - making it unusable)

[meehaws]

To be more precise, you can resume a Change Stream only when the resume token used for the change steam is present in the OPLOG. Oplot size is configurable by replSetResizeOplog and can have a minimum time to preserve entries.
If both size of oplog is reached and entries are older than the configured minimum hours, then the resume token will be removed. We want to handle that situation.

https://www.mongodb.com/docs/manual/reference/command/replSetResizeOplog/

[BartekGravity]

resumeTokens are now taken from the cursor which should prevent us from "losing" the resumeToken to the oplog if the applciation is running. I'm keeping this open as I need to implement handling cases where application is down and cannot use the token that is stored in the config.