Fix Mongo connector Atlas integration

[findepi]

Reverts #14988, reopens #1398

[findepi]

@ebyhr @mayankvadariya do you want to propose RN for this?

[huberty89]

I would rather provide quick fix (add config a property to disable my change) than just revert it. I will start working on it.
cc @kokosing

[ebyhr]

How about

Revert specifying `authorizedDatabasesOnly` and `authorizedCollections` options in MongoDB commands due to issue with Atlas integration.

[findepi]

Thanks for release notes @ebyhr

@huberty89 are you still working on a potentially better fix?

[huberty89]

@findepi Yes, I'm looking at possible solution for that

[findepi]

Since we broke Atlas integration in 405 and we didn't want that, let me mark this PR as a release blocker cc @trinodb/maintainers . I very much hope we merge @huberty89 's better fix, instead of this one, so treat this just as a placeholder.

[ebyhr]

FYI: The issue might not be specific to Atlas according to https://www.mongodb.com/docs/manual/release-notes/5.0-compatibility/#certain-commands-only-accept-recognized-parameters

Compatibility Changes in MongoDB 5.0
The following 5.0 changes can affect compatibility with older versions of MongoDB.

Certain Commands Only Accept Recognized Parameters
Starting in MongoDB 5.0, certain database commands raise an error if passed a parameter not explicitly accepted by the command. In MongoDB 4.4 and earlier, unrecognized parameters are silently ignored.

[Praveen2112]

https://www.mongodb.com/docs/manual/release-notes/5.0-compatibility/#certain-commands-only-accept-recognized-parameters

But in case of listingDatabase - authorizedDatabases is a recognized parameter right ?