Add database team to groups where milestones move forward

What does this MR do and why?

It looks like other teams are using this in their team groups to ensure that associated issues are correctly tagged for lables and the milestones move forward. Right now, we've had trouble with issues falling off of our issue board because the milestones are incorrect, so we're hoping to use this going forward!

Expected impact & dry-runs

• Schedule-sync: https://gitlab.com/gitlab-org/quality/triage-ops/-/jobs/3785512161
• Schedule Dry Run Pipeline: https://gitlab.com/gitlab-org/quality/triage-ops/-/pipelines/780182860

FYI - there's also a failing dry-run:custom job, I misread the docs and mistakenly kicked that off when I meant to use the schedule.

Action items

• [-] If adding environment variables for reactive processors, update config/triage-web.yaml and .gitlab/ci/triage-web.yml
• (If applicable) Add documentation to the handbook pages for Triage Operations =>
• (If applicable) Identify the affected groups and how to communicate to them:
  • /cc @person_or_group => gitlab-org/database-team
  • Relevant Slack channels => #g_database
  • Engineering week-in-review