docs(governance): adopt Community Specification license framework

[imran-siddique]

What changed

Implements the remaining Linux Foundation Community Specification framework work requested after #127.

Required framework files

Adds a dedicated Governance/ directory containing:

• CLA.md — Community Specification Contributor License Agreement, linked to TRACE's existing governance, contribution, and Code of Conduct policies
• COMMUNITY-SPECIFICATION-LICENSE.md — unmodified Community Specification License 1.0 text
• Scope.md — TRACE's technical scope and explicit exclusions, defining the bounds of specification patent obligations
• Notices.md — Code of Conduct contact, license-acceptance template, withdrawals, and patent-exclusion notices
• License.md — file-category map for Community Specification License 1.0, Apache-2.0 source code, and CC BY 4.0 documentation

Governance follow-up

Adds the Community Specification Ways of Working due-process principles requested in the unresolved review comment on #127:

• openness
• lack of dominance
• balance
• coordination and harmonization
• consideration of views and objections
• written procedures

It also states that TRACE Final status is the Community Specification License's Approved Specification status and links approval to the new Scope.

License consistency

Updates LICENSE, GOVERNANCE.md, CONTRIBUTING.md, CHARTER.md, the README badges, and the v0.2 specification metadata so the repository consistently applies:

• Community Specification License 1.0 to specification materials and the normative schema
• Apache License 2.0 to source code, tests, examples, and workflows
• CC BY 4.0 to non-specification documentation
• previously granted CC BY 4.0 rights to earlier specification publications

Why

PR #127 adopted the LF governance structure but used Apache-2.0 for both source code and specification text. The requested Community Specification framework requires a distinct specification license, a defined technical Scope, contributor agreement, notices mechanism, and explicit license map.

Validation

• python -m pytest -q: 339 passed, 1 skipped
• git diff --check: clean
• verified no stale references to the temporary numbered governance filenames
• Community Specification License text copied verbatim from CommunitySpecification/Community_Specification at commit 8a05e46d768ac0525af882b619c42f3380a9e869

Follow-up to #127.

[jorydotcom]

TY @imran-siddique - LGTM