feat!: Merge LDAP Teams Sync and Channels Sync into a new Rooms Sync section

[matheusbsilva137]

Proposed changes (including videos or screenshots)

• Merge "Teams Sync" and "Channels Sync" LDAP settings into a new "Room Sync" section that is capable of syncing channels, groups and teams;
• Update settings' names and descriptions to reflect the new organization;
• Improve rooms sync performance by having a single LDAP search request per user (instead of one per membership);
• Stop supporting the #{groupName} replacement in the LDAP Sync Rooms "Search Filter" (since the filter is now applied once per user);
• Fixed issue with Channel Sync only working in case the filter was applied to the memberOf field (RC didn't bind to the admin before applying the LDAP search request to get user groups, so only the logged in user itself would be visible).

---

More details about settings transition to the new organization

Old setting	New Setting
LDAP_Sync_User_Data_Channels	LDAP_Sync_User_Data_Rooms
LDAP_Sync_User_Data_Channels_Admin	LDAP_Sync_User_Data_Rooms_Admin
LDAP_Sync_User_Data_Channels_Filter	LDAP_Sync_User_Data_Rooms_Filter
LDAP_Sync_User_Data_Channels_BaseDN	LDAP_Sync_User_Data_Rooms_BaseDN
LDAP_Sync_User_Data_ChannelsMap	LDAP_Sync_User_Data_RoomsMap
LDAP_Sync_User_Data_Channels_Enforce_AutoChannels	LDAP_Sync_User_Data_Rooms_Auto_Leave
LDAP_Teams_Name_Field	LDAP_Group_Name_Field
LDAP_Enable_LDAP_Groups_To_RC_Teams	Removed (use LDAP_Sync_User_Data_Rooms instead)
LDAP_Groups_To_Rocket_Chat_Teams	Removed (use LDAP_Sync_User_Data_RoomsMap instead)
LDAP_Validate_Teams_For_Each_Login	Removed (use LDAP_Validate_Rooms_For_Each_Login instead)
LDAP_Teams_BaseDN	Removed (use LDAP_Sync_User_Data_Rooms_BaseDN instead)
LDAP_Query_To_Get_User_Teams	Removed (use LDAP_Sync_User_Data_Rooms_Filter instead)

Settings comparison (before and after):

---

Caution

Teams sync must be reconfigured using the "Rooms Sync" setting
Channels sync must also be reconfigured in case the #{groupName} replacement (which is not supported anymore) was being used -- prefer filtering by the member attribute in groups instead of using the memberOf field to avoid this.

Issue(s)

Steps to test or reproduce

Demo:

ldap-rooms-sync-test.webm

Further comments

CORE-402

[dionisio-bot]

Looks like this PR is not ready to merge, because of the following issues:

• This PR is missing the 'stat: QA assured' label

Please fix the issues and try again

If you have any trouble, please check the PR guidelines

[changeset-bot]

⚠️ No Changeset found

Latest commit: 62b6189

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 55.55%. Comparing base (d2530d3) to head (62b6189).

Additional details and impacted files

@@                Coverage Diff                @@
##           release-7.0.0   #32390      +/-   ##
=================================================
- Coverage          55.56%   55.55%   -0.02%     
=================================================
  Files               2408     2408              
  Lines              53019    53019              
  Branches           10902    10902              
=================================================
- Hits               29460    29453       -7     
- Misses             20941    20951      +10     
+ Partials            2618     2615       -3     

Flag	Coverage Δ
e2e	55.02% <ø> (-0.02%)	⬇️
unit	72.86% <ø> (-0.03%)	⬇️

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

[pierre-lehnen-rc]

The #{groupName} variable no longer exists for this search, so this default value is guaranteed to be invalid.

Also: change this into a dynamic setting with one default value for AD and another for non-AD, in the same way as some other settings here already work.