Move content moderation queues out of Webmasters to separate project

Problem/Motivation

- Webmasters issue queue has become too big. And it will grow bigger with the new sections being added to the site, which require moderation.
- Different people are interested in different parts of the issue queue, smaller queue will make it easier to concentrate on the stuff you care about. And people won't need to spend so much time deleting email notifications from issues they don't care about.
- New people who start contributing to the queue are often overwhelmed by its size and all the various things it has inside. So they stick to one specific component and do not look anywhere else. While if the queue was smaller and had only content-related issues, they would be interested to start helping with more components.
- Having smaller queue, team leads and clear documentation should help us get more people helping with the content queues, and they do need help and more people.

Proposed resolution

First mentioned in this issue: #1794810: Documenting team leaders for webmasters issue queue components.
Proposed solution is to move content queues our of webmasters to a separate project. With the following components for a start:

• Services listing,
• Training listing,
• Books listing,
• Case studies,
• Front page promotion,
• Planet Drupal
• Other

Implementation details

To automate the process of moving issues around we can probably use SQL script, similar to recently used in this issue: #1666886: Please help with renaming components of existing issues