Propose more metadata for development pages

What does this MR do?

These pages in the docs/development directory did not have stage / group metadata . When scanning through these pages, I saw links to MRs or discussion of general topics that implied a possible stage / group assignment.

The following people would see their page count increase because of the metadata assignments currently proposed:

• @axil - for devopsenablement :: groupdatabase (there were a lot of DB-related pages in this directory), groupmemory
• @aqualls - for devopsgrowth :: groupactivation
• @marcia - for devopscreate :: groupsource code, groupknowledge
• @mjang1 - for devopsmanage :: ~"group::import", ~"group::access", Category:Value Stream Management
• @ngaskill - for devopsprotect :: ~"group::container security"
• @rdickenson - for devopssecure - I guessed on the groups in at least one case, but I felt reasonably confident it was Secure
• unassigned - for devopsenablement :: infrastructure

MANY OF THESE WERE GUESSES. Use your judgment.

Screenshots (strongly suggested)

Does this MR meet the acceptance criteria?

Conformity

• Changelog entry
• Documentation (if required)
• Code review guidelines
• Merge request performance guidelines
• Style guides
• Database guides
• Separation of EE specific content

Availability and Testing

• Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process.
• Tested in all supported browsers
• Informed Infrastructure department of a default or new setting change, if applicable per definition of done

Security

If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:

• Label as security and @ mention @gitlab-com/gl-security/appsec
• The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
• Security reports checked/validated by a reviewer from the AppSec team