Records that the operator granted this config's connected account access to one provider-side resource — a file or folder chosen in the provider's picker.

Needed for scopes that don't determine reach on their own: Google's `drive.file` grants access to nothing except files Fruxon created or the user explicitly picked, so without this list such a connection can't touch a single pre-existing file. This mirrors a grant that actually lives at the provider — picking the file in the Picker is what grants it; this call records that it happened so the config page can show it and, later, so a tool call can pre-flight against it. Recording a resource here does <b>not</b> grant anything, and re-posting an existing id refreshes its stored name rather than erroring. Deliberately separate from the anonymous `oauth/authentication-completed` callback, which records the same fact from the mid-run OAuth redirect and is keyed on an encrypted flow token. This one is an authenticated operator action against a specific config.

curl -X POST "https://api.fruxon.com/v1/tenants/string/integrations/string/configs/497f6eca-6276-4993-bfeb-53cbbbba6f08/resources" \  -H "Content-Type: application/json" \  -d '{    "id": "string"  }'

{
  "items": [
    {
      "id": "string",
      "displayName": "string",
      "kind": "string",
      "grantedAt": 0
    }
  ],
  "nextPageToken": "string",
  "totalCount": 0
}

{
  "type": "string",
  "title": "string",
  "status": 0,
  "detail": "string",
  "instance": "string",
  "property1": null,
  "property2": null
}

{
  "type": "string",
  "title": "string",
  "status": 0,
  "detail": "string",
  "instance": "string",
  "property1": null,
  "property2": null
}