Add `group::database` to team triage package

Sample output from dry-run

The following issue would be created for the rule **Collate "group::database" issues requiring attention**:

>>>
* Title: 2019-10-17 - Triage report for "group::database"
* Description: Hi, @joshlambert @craig-gomes

This is a group or stage level triage package that aims to summarize
the feature proposals and bugs which have not been scheduled or triaged.
For more information please refer to the handbook:
- https://about.gitlab.com/handbook/engineering/quality/triage-operations/index.html#triage-packages

Scheduling the workload is a collaborative effort by the Product Managers
and Engineering Managers for that group. Please work together to provide
a best estimate on priority and milestone assignments. For each issue please:

- Determine if the issue should be closed if it is no longer relevant or a
duplicate.
- If it is still relevant please assign either a best estimate versioned
milestone, the %Backlog or the %"Awaiting further demand" milestone.
- Specifically for ~bug, if there is no priority or clarity on a versioned
milestone, please add a Priority label. Priority labels have an estimate
SLO attached to them and help team members and the wider community understand
roughly when it will be considered to be scheduled.
  - https://docs.gitlab.com/ee/development/contributing/issue_workflow.html#priority-labels
- Once a milestone has been assigned please check off the box for that issue.
- Please work with your team to complete the list by the due date set.

### Bug Section

For the following bugs. Please either close or assign either a versioned
milestone, the %Backlog or the %"Awaiting further demand" milestone and
ensure that a priority label is set.

#### Heatmap for all bugs

Bugs for their priority and severity label are counted here. Every bug should
have severity and priority labels applied. Please take a look at the bugs
which fall into the columns indicating that the priority or severity labels
are currently missing.


|| ~S1 | ~S2 | ~S3 | ~S4 |
|----|----|----|----|----|
| ~P1 | 0 | 0 | 0 | 0 |
| ~P2 | 0 | 0 | 0 | 0 |
| ~P3 | 0 | 0 | 0 | 0 |
| ~P4 | 0 | 0 | 0 | 0 |
| ~"No priority" | 0 | 0 | [1](https://gitlab.com/gitlab-org/gitlab/issues?state=opened&label_name%5B%5D=group%3A%3Adatabase&label_name%5B%5D=bug&label_name%5B%5D=%22No+priority%22&label_name%5B%5D=S3) | 0 |

----



#### Unscheduled ~bug (non-customer)

- [ ] #33084 12.2.5 -> 12.3.1 Database migration failed: Multiple indexes found ~"S3", ~"bug", ~"database", ~"devops::enablement", ~"group::database"

----


/label ~"group::database"
/label ~"triage-package"
/due in 7 days
/assign @joshlambert @craig-gomes

---

This is a group level triage package that aims to collate the latest bug reports (for frontend and otherwise) and feature proposals.
For more information please refer to the handbook:
- https://about.gitlab.com/handbook/engineering/quality/triage-operations/index.html#triage-packages