[3.13.0] Deleting a team breaks private channels and groups from the web (Team not found)

Description:

I really liked the new team function but unfortunately doing some tests to test all its functions I have broken access to all users of a channel or private group that I added to the team. This happened after deleting the team, but I clarify that the existing channels or groups were not deleted, they appear perfectly in my chat list but I cannot access them.

Note: This problem is only evident from the web, these groups and channels can be accessed from the mobile client.

Steps to reproduce:

1. Create a public team.
2. Add channels and private groups that you previously created.
3. Delete team without deleting channels and groups.
4. Team not found error when I access previously created groups.

Expected behavior:

Actual behavior:

Server Setup Information:

• Version of Rocket.Chat Server: 3.13.0
• Operating System: ubuntu
• Deployment Method: tar
• Number of Running Instances: 1
• DB Replicaset Oplog: Yes
• NodeJS Version: v12.18.4
• MongoDB Version: 4.0.23

Client Setup Information

• Problem only from the web client

Additional context

Relevant logs:

I20210408-19:28:13.007(-4) server.js:204 Meteor ➔ method listCustomUserStatus -> userId: dieWKCepwPyB7ppuh, arguments: [] I20210408-19:28:13.011(-4) server.js:204 API ➔ debug POST: /api/v1/method.call/apps:is-enabled I20210408-19:28:13.012(-4) apps/is-enabled { id: 'ocovFcBMHRnhSfAP2', clientAddress: 'x.x.x.x', httpHeaders: { connection: 'upgrade', host: 'host.rocket', 'x-real-ip': 'y.y.y.y', 'x-forward-for': 'x.x.x.x, y.y.y.y', 'x-forward-proto': 'http', 'x-nginx-proxy': 'true', 'content-length': '92', 'x-forwarded-for': 'x.x.x.x', 'sec-ch-ua': '"Google Chrome";v="89", "Chromium";v="89", ";Not A Brand";v="99"', 'sec-ch-ua-mobile': '?0', 'user-agent': 'Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/89.0.4389.114 Safari/537.36', 'content-type': 'application/json', accept: '*/*', 'x-auth-token': 'K87gzY4WdCiB8rJbPuJb5mrnKiFQ9t4FUCx2UtwC3sD', 'x-requested-with': 'XMLHttpRequest', 'x-user-id': 'dieWKCepwPyB7ppuh', origin: 'https://host.rocket', 'sec-fetch-site': 'same-origin', 'sec-fetch-mode': 'cors', 'sec-fetch-dest': 'empty', referer: 'https://host.rocket/group/canal-de-3er-ano', 'accept-encoding': 'gzip, deflate, br', 'accept-language': 'es,en;q=0.9', cookie: '_ga=GA1.3.327307549.1611441325; _pk_id.2.b50b=270012176d838504.1617524616.; rocketchatscreenshare=chrome; rc_uid=dieWKCepwPyB7ppuh; SL_GWPT_Show_Hide_tmp=1; SL_wptGlobTipTmp=1; rc_token=K87gzY4WdCiB8rJbPuJb5mrnKiFQ9t4FUCx2UtwC3sD' }, userId: 'dieWKCepwPyB7ppuh' }

Start by reproducing the web-client flow: create a public team, add existing channels or private groups, delete the team, and open those rooms again. Compare the web behavior with the mobile client, then verify that the affected rooms remain accessible after deletion. The issue names no files or tests, so locating the relevant entry point requires repository exploration.