Require code owner approval

What does this MR do?

This allows users with a Premium license to require approval from code owners in a merge request.

For Premium installations it adds the following setting to the projects:

When enabled, one approval is required per matched CODEOWNER entry.

This looks like this on the MR widget:

On the MR edit screen the required code owners are mentioned like this:

What are the relevant issue numbers?

closes #4418 (closed)

Does this MR meet the acceptance criteria?

• Changelog entry added, if necessary
• Documentation created/updated via this MR
• Documentation reviewed by technical writer or follow-up review issue created
• Tests added for this feature/bug
• Tested in all supported browsers
• Conforms to the code review guidelines
• Conforms to the merge request performance guidelines
• Conforms to the style guides
• Conforms to the database guides
• Link to e2e tests MR added if this MR has Requires e2e tests label. See the Test Planning Process.
• EE specific content should be in the top level /ee folder
• For a paid feature, have we considered GitLab.com plans, how it works for groups, and is there a design for promoting it to users who aren't on the correct plan?
• Security reports checked/validated by reviewer