chore: update CODEOWNERS to implement a hierarchical authority structure

[nearlyforget]

Description

Update CODEOWNERS to implement a hierarchical authority structure and ensure comprehensive ownership of critical infrastructure and governance files.

Key changes:

• Hierarchical Approval: Explicitly added higher-ranked teams (maintainers, tech-council, governance-council) to files owned by lower-level teams (like devops-maintainers). This allows senior teams to provide "Code Owner" sign-off when necessary.
• Expanded DevOps Coverage: Updated devops-maintainers to cover additional tooling files (e.g., .pre-commit-config.yaml) and all lockfiles/manifests (e.g., uv.lock, package-lock.json, Cargo.lock) across the repository.
• Governance Alignment: Explicitly assigned /LICENSE and CODEOWNERS to the
  @Universal-Commerce-Protocol/governance-council for ecosystem-wide consistency.

Github Settings to control noise:

To ensure hierarchical authority without generating unnecessary email noise for senior teams, we will implement the following configuration in conjunction with this PR:

• Silent Team Notifications: Keep team-level notifications "silent" to prevent automated spam to the entire Tech Council or Governance Council.
• Automatic Team Member Assignment: Enable automatic assignment for the maintainers and DevOps-maintainer teams only. This ensures that only specifically auto-selected individuals receive direct notifications, preventing the entire team from being spammed for standard updates.
• For further details on how to configure independent notifications for team assignments, refer to the GitHub documentation on reducing review noise

Category (Required)

Please select one or more categories that apply to this change.

• Core Protocol: Changes to the base communication layer, global context, or breaking refactors. (Requires Technical Council approval)
• Governance/Contributing: Updates to GOVERNANCE.md, CONTRIBUTING.md, or CODEOWNERS. (Requires Governance Council approval)
• Capability: New schemas (Discovery, Cart, etc.) or extensions. (Requires Maintainer approval)
• Documentation: Updates to README, or documentations regarding schema or capabilities. (Requires Maintainer approval)
• Infrastructure: CI/CD, Linters, or build scripts. (Requires DevOps Maintainer approval)
• Maintenance: Version bumps, lockfile updates, or minor bug fixes. (Requires DevOps Maintainer approval)
• SDK: Language-specific SDK updates and releases. (Requires DevOps Maintainer approval)
• Samples / Conformance: Maintaining samples and the conformance suite. (Requires Maintainer approval)
• UCP Schema: Changes to the ucp-schema tool (resolver, linter, validator). (Requires Maintainer approval)
• Community Health (.github): Updates to templates, workflows, or org-level configs. (Requires DevOps Maintainer approval)

Related Issues

Checklist

• I have followed the Contributing Guide.
• I have updated the documentation (if applicable).
• My changes pass all local linting and formatting checks.
• (For Core/Capability) I have included/updated the relevant JSON schemas.
• I have regenerated Python Pydantic models by running generate_models.sh under python_sdk.

Screenshots / Logs (if applicable)

[nearlyforget]

@amithanda - can you please take a look?