feat(schemas): add MeshModel component and relationship summary filter/response schemas

[Amr-Shams]

Problem

MeshModel summary filter and response structs are currently maintained manually in downstream code, which creates drift and duplicate API shape definitions.

Proposal

Add schema definitions for:

• ComponentSummaryFilter
• ComponentSummary
• ComponentGroupEntry
• RelationshipSummaryFilter
• RelationshipSummary
• RelationshipGroupEntry

Include enum values for summary dimensions:

• component: by_model, by_category, by_registrant
• relationship: by_model, by_kind, by_type, by_subtype

Acceptance Criteria

• OpenAPI schema definitions added under the appropriate versioned construct files.
• Go and TypeScript generated models include the new types.
• Existing generation checks/tests pass.
• Downstream consumers can import generated types without hand-written duplicates.

Related

• meshkit PR: summary aggregation integration/tests

[welcome]

Thanks for opening this issue. A contributor will be by to give feedback soon. In the meantime, please review the Contributors' Welcome Guide, engage in the discussion forum, and be sure to join the community Slack.