Improve community channel communication

In the spirit of providing easier means for community members, especially core maintainers of community channels, such as conda-forge and bioconda, we need to evolve our abilities to record and track issues when they come up, especially when they are urgent in nature.

In the past this was solved through various media such as email, GitHub issues (e.g. in anaconda-issues), conda Slack, gitter (various channels) or personal connections. This isn't scalable and transparent and because of that a risk to the sustainability of the larger conda ecosystem.

As such @chenghlee and me propose a small evolution of the current system to do:

- [ ] add new issue form for hosting related issues (with https://github.com/conda/infra/labels/type%3A%3Ahosting preselected) with appropriate explanation to use severity labels
- [ ] add a new conda/infra team to the conda organization to be added as assignees to new issues
- [ ] add new hosting board that tracks issues with hosting label
- [ ] sync issues to Anaconda's Jira to the appropriate infrastructure team's project (with assignment if possible)
- [ ] document the communication process in the README of this repo
- [ ] disseminate this change with the various community channels
- [ ] mentioned it in the conda community meeting

Start with the repository README and review how hosting-related issues, labels, assignees, boards, and external tracking are currently handled. Use the checklist in this issue as the acceptance criteria: the communication process should be documented, the listed tracking and synchronization changes addressed, and the community channels informed.

Written by the indexing model from the issue text.