Redirect chatops requests to team channels

The production channel is for production incidents and operations, and
the infrastructure team are primarily responsible for it. Messages
asking to be added to chatops usually come to the attention of infra
before any other team. This leads to redundant attempts to re-validate
the legitimacy of the request, which could more easily be handled by a
fellow team member of the requester, in their channel.

SRE's on-call configure the production channel to alert them for every
new message, so chatops requests here are quite noisy.

doc/development/chatops_on_gitlabcom.md

@@ -21,7 +21,7 @@ To request access to Chatops on GitLab.com:
 
 1. Log into <https://ops.gitlab.net/users/sign_in> **using the same username** as for GitLab.com (you may have to rename it).
     1. You could also use the "Sign in with" Google button to sign in, with your GitLab.com email address.
-1. Ask in the [#production](https://gitlab.slack.com/messages/production) channel for an existing member to add you to the `chatops` project in Ops. They can do it by running `/chatops run member add <username> gitlab-com/chatops --ops` command in that channel.
+1. Ask one of your team members to add you to the `chatops` project in Ops. They can do it by running `/chatops run member add <username> gitlab-com/chatops --ops` command in the `#chat-ops-test` Slack channel.
 
 NOTE: **Note:**
 If you had to change your username for GitLab.com on the first step, make sure [to reflect this information](https://gitlab.com/gitlab-com/www-gitlab-com#adding-yourself-to-the-team-page) on [the team page](https://about.gitlab.com/company/team/).