[DNM] governanace and ownership updates

[rohitthakur2590]

Description

• What is being changed?
• Why is this change needed?
• How does this change address the issue?

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update
• Test update
• Refactoring (no functional changes)
• Development environment change
• Configuration change

Self-Review Checklist

• I have performed a self-review of my code
• I have added relevant comments to complex code sections
• I have updated documentation where needed
• I have considered the security impact of these changes
• I have considered performance implications
• I have thought about error handling and edge cases
• I have tested the changes in my local environment
• Existing playbook FQCNs are preserved (no renames without a redirect in meta/routing.yml)
• Deprecated parameters include a deprecated: block in DOCUMENTATION with removal version

Testing Instructions

Prerequisites

Steps to Test

Expected Results

Additional Context

Required Actions

• Requires documentation updates
• Requires downstream repository changes
• Requires infrastructure/deployment changes
• Requires coordination with other teams
• Blocked by PR/MR: #XXX

CasC Notification

• Not applicable — this change does not affect the CasC-monitored surface
• CasC Jira ticket created:
• CasC team tagged in this PR
• Migration guide provided (required for breaking changes)

Screenshots/Logs