Chore: Remove role requirement to use change streams

[sampaiodiego]

Proposed changes (including videos or screenshots)

We used to require the clusterMonitor role to be able to use Change Streams because we performed a serverStatus command, to be able to check if the requirements for change streams are met (like using wired tiger for example). But since our minimum MongoDB supported version is now 4.2, and MMAPv1 was removed on this version, there is no need to check that.

The new approach is just try to use change streams, if it fails for any reason, fallback to oplog.

If oplog fails as well, we're now halting the process, since it wasn't able to establish a connection for reading real time data, something that is crucial for the application. An additional check was added to make sure $MONGO_OPLOG_URL is pointing to the local database.

Issue(s)

Closes #20017

Steps to test or reproduce

Further comments

[codecov]

Codecov Report

Merging #27281 (6b43763) into develop (54b2b7f) will increase coverage by 1.00%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           develop   #27281      +/-   ##
===========================================
+ Coverage    40.24%   41.25%   +1.00%     
===========================================
  Files          847      819      -28     
  Lines        18430    17933     -497     
  Branches      2052     1988      -64     
===========================================
- Hits          7417     7398      -19     
+ Misses       10727    10247     -480     
- Partials       286      288       +2     

Flag	Coverage Δ
e2e	41.25% <ø> (+1.00%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

[geekgonecrazy]

Just for context before this.. frequently people who start using permissions with mongo but missed this permission start encountering reactivity issues that look like Rocket.Chat is buggy.

But then as soon as they added it things started working fine. One common one was connectivity services, but also anything that depended on change stream to populate setting cache.

The permission is only needed for something informational that provides little value. So requiring is costing way more than we lose by removing it.

IMO for customer experience this is a must for the release. If a release wasn't coming I'd argue for a patch that's how impactful it is.