brand our bots consistently

Our bots call themselves a few different things

- conda-forge-admin
- conda-forge-webservices[bot]
- "conda-forge-linting service"
- "conda-forge rerendering service"
- conda-forge-currator[bot]
- "friendly automated conda-forge-webservice"
- _others I am forgetting..._

It would be nice to decide on a consistent name and try to ensure that is used as much as possible in our tools. Some of this is unavoidable due to github account / app names, but I think we can get pretty close. I am excluding the `regro-cf-autotick-bot` from this discussion for now.

My vote for the name is `conda-forge-admin` since folks bump this account for the webservices commands.

To-do Items:

- [ ] decide on a name (likely `conda-forge-admin`)
- [ ] use the `conda-forge-admin` token as much as possible to make comments on PRs / issues / etc.
- [ ] set the git committer to `conda-forge-admin` in various spots (e.g., docker images, scripts, git CLI, github API calls, etc.)
- [ ] use the `conda-forge-admin` token as much as possible to make commits to feedstocks
- [ ] change text of comments made by bots to refer to themselves as the `conda-forge-admin`

cc @conda-forge/core