Updates to relations in API docs

[pwizla]

This PR:

• updates the docs for connect, disconnect, and set to use documentIds instead of ids
• adds a callout to Document Service API with a short example so that users know it works "the same" as with the REST API

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
documentation	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jun 11, 2024 3:11pm

[Marc-Roig]

Docs looks good !

There are more complex scenarios that we might want to document , maybe they are more advanced and not as useful for the majority, but they might be useful to know.

• Relation from Category (i18n off) -> Article (i18n on):
  In this situation you can select which locale you are connecting

data: {
    categories: {
      connect: [
        { documentId: 'z0y2x4w6v8u1t3s5r7q9onm', locale: 'en' },
       { documentId: 'z0y2x4w6v8u1t3s5r7q9onm', locale: 'fr' }, // Connect to the same document id but different locale
      ]
   }
}

• Relation from Category (D&P off) -> Article (D&P on):
  (Probably less relevant than the first one)

data: {
    categories: {
      connect: [
        { documentId: 'z0y2x4w6v8u1t3s5r7q9onm', status: 'draft' },
       { documentId: 'z0y2x4w6v8u1t3s5r7q9onm', status: 'published' }, // Connect to the same document id but different publication states
      ]
   }
}

Note, on any api we expose the "documentId", the user will be able to reference both locale and status .