feat: improve type safety for siblingData in field types

[Rot4tion]

Summary

Improves TypeScript type safety for siblingData across field configuration types by introducing a StripRelationships utility type that removes populated relationship objects, keeping the ID type (number or string) base on database config.

const siblingData = {
  creator: 1,                    // Relationship field
  _status: 'draft',
  title:"abc",
  updatedAt: '2025-12-11T07:52:22.115Z',
  createdAt: '2025-12-11T07:13:24.433Z',
  attributes: [3, 2],            // Relationship hasMany
  description: {                 // RichText field
    root: {
      type: 'root',
      children: [...],
    }
  },
}

} // RichText field


// Before (Incorrect Types)
type SiblingData = {
  [key: string]: any
} | undefined

// Or with Partial<TData>:
type SiblingData = {
  creator: number | User | undefined      // ❌ Includes populated object
  attributes?: (number | Attribute)[]     // ❌ Includes populated objects
  ...
}


// After (Correct Types)

type SiblingData = {
  id: number | undefined
  creator: number | undefined              // ✅ ID only
  title: string | undefined
  description: {
    [k: string]: unknown
    root: {
      type: string
      children: { type: any; version: number }[]
      direction: 'rtl' | 'ltr' | null
      format: '' | 'center' | 'left' | 'right' | 'start' | 'end' | 'justify'
      indent: number
      version: number
    }
  } | undefined
  attributes?: number[] | null             // ✅ IDs only
  updatedAt: string | undefined
  createdAt: string | undefined
   _status?: "draft" | "published" | null
}

[AlessioGr]

TData !== TSiblingData if you're in a group field. I'd rather have it typed weakly (any) than potentially incorrectly

[Rot4tion]

i see the issue, pls check my new commit