Move Governance pages to /-/automate/governance

What does this MR do and why?

#627833 (closed) moved the group Governance item into the AI sidebar menu. The pages themselves still lived at settings/gitlab_duo/governance. On self-managed, the group URL sits under a parent path that returns 404.

This MR moves both Governance pages to /-/automate/governance, next to the other AI menu items (agents, flows, MCP servers). Governance keeps its own controller and Vue app. It is not folded into the Duo Agent Platform SPA.

References

• Resolves #630631 (closed)
• Follow-up to #627833 (closed)
• Related: #629430, #630632 (closed), #630817

Screenshots or screen recordings

The visible differences are the URL, plus, on the project page, no Settings layout (search box) and no GitLab Duo breadcrumb.

Before	After

How to set up and validate locally

1. As an owner of a top-level group with AI features licensed, go to the group and select AI > Governance. The URL is /groups/<group>/-/automate/governance and the menu item is highlighted.
2. Visit /groups/<group>/-/settings/gitlab_duo/governance?tab=agent-artifacts. You are redirected to /groups/<group>/-/automate/governance?tab=agent-artifacts.
3. Visit /<group>/<project>/-/automate/governance. The page renders without the Settings search box or the GitLab Duo breadcrumb.
4. Visit /<group>/<project>/-/settings/gitlab_duo/governance?tab=agent-artifacts. You are redirected to the new project URL, and the query string is kept.
5. Check that /-/automate/agents, /-/automate/flows, /-/automate/mcp-servers, and /-/automate/agent-sessions still load the Agent Platform app.

MR acceptance checklist

Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.