[rocketmq-connect-mongodb]mongodb-connect can't hand the opt-log of mongodb

The issue tracker is **ONLY** used for bug report and feature request.

Any question or RocketMQ proposal please use our [mailing lists](http://rocketmq.apache.org/about/contact/).

**BUG REPORT**

1. Please describe the issue you observed:
mongodb-connect can't hand the opt-log of mongodb when the config contains the option 'interestDbAndCollection'.
- What did you do (The steps to reproduce)?

- What did you expect to see?

- What did you see instead?

2. Please tell us about your environment:

3. Other information (e.g. detailed explanation, logs, related issues, suggestions how to fix, etc):

**FEATURE REQUEST**

1. Please describe the feature you are requesting.

2. Provide any additional detail on your proposed use case for this feature.

2. Indicate the importance of this issue to you (blocker, must-have, should-have, nice-to-have). Are you currently using any workarounds to address this issue?

4. If there are some sub-tasks using -[] for each subtask and create a corresponding issue to map to the sub task:

- [sub-task1-issue-number](example_sub_issue1_link_here): sub-task1 description here,
- [sub-task2-issue-number](example_sub_issue2_link_here): sub-task2 description here,
- ...

Start by locating the mongodb-connect implementation and the handling of the `interestDbAndCollection` option. Reproduce the configuration described in the issue and compare its behavior with MongoDB's oplog; done means the connector handles the oplog correctly when that option is present.

Written by the indexing model from the issue text.