[feat] Add JSONSchemas

[sfc-gh-bnisco]

TL;DR

Added JSON schema definitions for the Component Gallery registry system.

What changed?

• Created compiled.schema.json which defines the structure for the compiled components catalog
• Created component.schema.json which defines the structure for individual component submissions
• Both schemas include detailed validation rules for component metadata including:
  • Required fields (title, author, links, categories)
  • Format validation for URLs, dates, and other fields
  • Constraints on field lengths and content patterns
  • Predefined category options for components

Why make this change?

These schema definitions provide a standardized structure for component submissions and the compiled catalog, ensuring:

1. Consistent data format for all components in the gallery
2. Proper validation of component metadata
3. Clear requirements for contributors submitting new components
4. Structured format for metrics and ranking data
5. Foundation for automated validation in the submission process

[sfc-gh-bnisco]

• [feat] Add contributing guidelines for the registry #8
• [feat] Add initial compiled components.json file #7
• [feat] Add all components/registry/components/*.json files #6
• [feat] Add GH Workflows #5
• [feat] Add component directory scripts #4
• [feat] Add JSONSchemas #3 👈 (View in Graphite)
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[mayagbarnes]

Nit: Since starsScore is always computed (never null), the schema could reflect this