Update CODEOWNERS, especially lines for Database

What does this MR do?

These changes to the CODEOWNERS file include:

• Splitting off the non-auto-updated docs lines from the lines we overwrite each time from the rake task, so the catchall directory lines in the file are not overwritten.
• Re-running the task to add in updates.
• Re-running the task with @aqualls marked as the (temporary) TW for groupdatabase, so @marcia receives fewer pings in her absence.

Observation: someone definitely tidied the directories, previously, that contained nothing but files belonging to the same owner. While it shortens the output (and I want us to move in that direction eventually) the script doesn't currently support this shortened output. In the interest of keeping this huge set of lines easy to update, for now we'll still to the full-and-slightly-redundant output.

NOT included:

• the change to the lib/tasks/gitlab/tw/codeowners.rake file itself, changing group ownership from Marcia to Amy. That change incurs a long backend pipeline and is split out into Change TW for Database from Marcia to Amy (!82625 - merged).

Related issues

• Related to !77715 (merged) where the rake task was created.

Author's checklist

• Consider taking the GitLab Technical Writing Fundamentals course.
• Follow the:
  • Documentation process.
  • Documentation guidelines.
  • Style Guide.
• Ensure that the product tier badge is added to topic's h1.
• Request a review based on:
  • The documentation page's metadata.
  • The associated Technical Writer.

If you are only adding documentation, do not add any of the following labels:

• ~"frontend"
• ~"backend"
• ~"type::bug"
• ~"database"

These labels cause the MR to be added to code verification QA issues.

Review checklist

Documentation-related MRs should be reviewed by a Technical Writer for a non-blocking review, based on Documentation Guidelines and the Style Guide.

• If the content requires it, ensure the information is reviewed by a subject matter expert.
• Technical writer review items:
  • Ensure docs metadata is present and up-to-date.
  • Ensure the appropriate labels are added to this MR.
  • If relevant to this MR, ensure content topic type principles are in use, including:
    • The headings should be something you'd do a Google search for. Instead of Default behavior, say something like Default behavior when you close an issue.
    • The headings (other than the page title) should be active. Instead of Configuring GDK, say something like Configure GDK.
    • Any task steps should be written as a numbered list.
    • If the content still needs to be edited for topic types, you can create a follow-up issue with the docs-technical-debt label.
• Review by assigned maintainer, who can always request/require the reviews above. Maintainer's review can occur before or after a technical writer review.
• Ensure a release milestone is set.