Adds list view quick actions table and navigation to manage projects and groups

What does this MR do?

This MR adds tables and navigation steps to Working with projects and Groups pages. The tables list which quick actions menu items are available for managing groups and projects depending on the state of the group or project.

Follow-up questions:

• Do we call this menu the "<Groups/Projects> list view menu"?
• Are the documented navigation steps in this MR the only way to access these quick actions from a list view?
• Do we want to call these actions "quick actions"?

I'm open to standardizing this UI, but not sure if that's necessary. If we did, I think something like Quick actions menu might work for the UI term itself. The selectable actions themselves could remain quick actions, but we'd need to distinguish the menu quick actions from our guidance on quick actions that are executable as keyboard commands.

Related issues

&18829 (comment 2716837707)

Author's checklist

• Optional. Consider taking the GitLab Technical Writing Fundamentals course.
• Follow the:
  • Documentation process.
  • Documentation guidelines.
  • Style Guide.
• If you're adding a new page, add the product availability details under the H1 topic title.
• If you are a GitLab team member, request a review based on:
  • The documentation page's metadata.
  • The associated Technical Writer.

If you are a GitLab team member and 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.

Reviewer's 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 you aren't sure which tech writer to ask, use roulette or ask in the #docs Slack channel.

• 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.
  • Ensure a release milestone is set.
  • 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.