Can't use term for search in account custom fields if channel matches the same name.

Description:

Can't use specific term for search which are in account custom fields and channel matches the same term.

We create a custom field for users so everybody can search for a department name and bring the list of the people which works there. We thought about using a custom field with the department name because we use an IM app which the ppl were listed in groups as departments like HR, IT etc. So if you need to talk with someone in IT you would go to the app and see in the IT group who was online without the need to know who works in there.
We're deploying Rocket.Chat at our work and everybody liked the tool, but "the major concern" is still not being able to list all people online as other (old) IM apps and setting the custom field department through syncing LDAP is the perfect solution for now as anyone can search the term IT and it will bring all ppl with the department IT without knowing who works there.

Steps to reproduce:

1. We create a channel with the name of el-contabilidade;
2. Create a custom field to sync from LDAP the field department and show it in the user info
3. Search "contabilidade" and it will bring only the channel and not the users
4. If you aren't a member of the channel with the same name it will list the users with the custom field department "contabilidade" and the channels that matches it if it's public.

Expected behavior:

If I search for a term it should only bring the results of the people with the custom field which matches the term and the public channels.

Actual behavior:

If I search for a specific term and we have a channel which contains the specific/part of it and you're a member of the channel
it will bring only the channel and not the other people with the custom field filled. If I use the Directory Listing it works as expected.

Server Setup Information:

• Version of Rocket.Chat Server: 3.10.0
• Operating System: Ubuntu
• Deployment Method: Docker
• Number of Running Instances: 1
• DB Replicaset Oplog: Enabled
• NodeJS Version: v12.18.4
• MongoDB Version: 4.0.18

Client Setup Information

• Desktop App or Browser Version: Desktop App and Chrome Version 87.0.4280.88
• Operating System: macOS but we tested in Windows 10 too.

Additional context

It's a minor bug but still a bug in our view because it will only affect a small percentage of users but it would affect new users which in our case is basically all our users as they are being presented to Rocket.Chat only now.

Start by reproducing the search with a channel name matching a user custom-field value, comparing the results for channel members and non-members. Trace the search entry point and the Directory Listing behavior to find where matching results are filtered. Done means a search returns the matching users and permitted public channels together.