feat(label-sync): add area:lodging, area:food, and area:shopping labels with descriptions

[damaz91]

Description

Adds the area:lodging, area:food, and area:shopping domain labels to org-tools/label-sync/labels/triage-labels.yml to support triage routing, saved issue/PR search queries, and team notifications for Domain Technical Councils (DTCs). Also adds descriptions across all area:* labels and governance review labels (gov:needs-tc-review, gov:needs-gc-review).

Label Details, Colors & Descriptions

• area:payments (#0052CC - Royal Blue): Issues and pull requests related to the Payments vertical
• area:shopping (#BF3989 - Magenta / Berry): Issues and pull requests related to the Shopping vertical
• area:lodging (#1A7F37 - Emerald Green): Issues and pull requests related to the Lodging vertical
• area:food (#E36209 - Bright Orange): Issues and pull requests related to the Food ordering vertical
• gov:needs-tc-review (#D93F0B - Red): Requires review and approval from the Technical Council
• gov:needs-gc-review (#FDE5BE - Peach): Requires review and approval from the Governance Council

Category (Required)

• 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

N/A

Checklist

• I have followed the Contributing Guide (including Conventional Commits title requirements and ! for breaking changes).
• I have updated the documentation (if applicable).
• My changes pass all local linting and formatting checks.
• I have added tests that prove my fix is effective or that my feature works.
• New and existing unit tests pass locally with my changes.
• (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)

test_live_configuration_files (__main__.TestLabelSync.test_live_configuration_files)
Verify that live general-labels.yml and triage-labels.yml are syntactically valid and conflict-free ... ok
  ✓ Verify that live general-labels.yml and triage-labels.yml are syntactically valid and conflict-free

[ptiper]

LGTM! Thanks Federico. As a quick follow-up, we could consider adding description fields across all four area:* labels (including area:payments) to match the other triage and general labels that define descriptions.