Database reviewers

With the review roulette in place (https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/24938), we now have the ability to suggest reviewers and maintainers for review/merge.

For database, I would like to nominate @yguo, @cshobe and @fjsanpedro for database reviewers.

An example of how the result of the review roulette looks like is: https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/7361#note_101230798

A database reviewer is going to show up for any MR labeled Database. The idea is for the reviewer to take a first stab at the MR before passing it on to a maintainer. Note the danger roulette is only a suggestion and the MR author may pick other people as per https://docs.gitlab.com/ee/development/code_review.html.

.gitlab/issue_templates/Feature proposal.md

@@ -2,9 +2,10 @@
 <!--- What problem do we solve? -->
-### Target audience
-<!--- For whom are we doing this? Include either a persona from https://design.gitlab.com/getting-started/personas or define a specific company role. e.a. "Release Manager" or "Security Analyst". Use the persona labels as well https://gitlab.com/groups/gitlab-org/-/labels?utf8=%E2%9C%93&subscribed=&search=persona%3A -->
+### Intended users
+<!-- Who will use this feature? If known, include any of the following: types of users (e.g. Developer), personas, or specific company roles (e.g. Release Manager). It's okay to write "Unknown" and fill this field in later.
+Personas can be found at https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/ -->
 ### Further details