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

[Junnygram]

This PR introduces OpenAPI schemas for MeshModel component and relationship summary filters.

• Added ComponentSummaryFilter, ComponentSummary, and ComponentGroupEntry to v1beta2/component/api.yml.
• Added RelationshipSummaryFilter, RelationshipSummary, and RelationshipGroupEntry to v1beta2/relationship/api.yml.
  Fixes define openapi schemas for meshmodel component and relationship summary filters #747

[gemini-code-assist]

Code Review

This pull request introduces new schemas for component and relationship summaries and filters in the v1beta2 API. The review feedback recommends defining the "annotations" filter as a boolean type for consistency and updating the "include" enum values from snake_case to camelCase to align with the summary object properties and server-side JSON tags.

[gemini-code-assist]

The annotations filter is defined as a string enum with values "true" and "false". To maintain consistency with other boolean filters in this schema (such as greedy in RelationshipSummaryFilter) and to follow standard OpenAPI practices, this should be defined as type: boolean. Additionally, ensure that corresponding endpoints in other API versions (like v1beta1) are updated consistently.

        annotations:
          type: boolean
          description: "Filter by annotations."

References

1. Schemas within the meshery/schemas repository should maintain a uniform pattern across all constructs.
2. When updating an API endpoint, ensure that corresponding endpoints in other API versions (e.g., v1beta1 and v1beta2) are updated consistently to match exactly.

[gemini-code-assist]

The enum values for the include array use snake_case, while the corresponding properties in the ComponentSummary object use camelCase. OpenAPI schema properties for payloads must exactly match the json tags of the corresponding server-side structs to prevent silent field dropping. If the server implementation uses camelCase, these enum values should be updated to match. Ensure this is applied consistently across API versions.

            enum: ["byModel", "byCategory", "byRegistrant"]

References

1. OpenAPI schema properties for payloads must exactly match the json tags of the corresponding server-side structs.
2. Field name casing in generated structs must match the casing in the source of truth, even if this leads to inconsistencies across different structs.
3. When updating an API endpoint, ensure that corresponding endpoints in other API versions are updated consistently.

[gemini-code-assist]

The enum values for the include array use snake_case, whereas the RelationshipSummary object uses camelCase. Casing in the schema must match the server-side source of truth (json tags). Using camelCase for these enum values would improve consistency across the API definition and match the server implementation. Ensure other API versions are updated to match.

            enum: ["byModel", "byKind", "byType", "bySubType"]

References

1. OpenAPI schema properties for payloads must exactly match the json tags of the corresponding server-side structs.
2. Field name casing in generated structs must match the casing in the source of truth.
3. When updating an API endpoint, ensure that corresponding endpoints in other API versions are updated consistently.