Include conversation ID directly in API response

Problem
When using API endpoints like create draft or create message, the conversation ID is nested in the _links.related.conversation structure rather than in the direct response path, requiring additional parsing to construct conversation URLs.

Request
Include conversation ID directly in the API response path so developers can more easily construct conversation links without having to extract it from nested link references.