Update response and types for api server update (#1340)

# Enhance Profile API with Social Account Usernames and Farcaster Support

## Description

This PR enhances the profile API by adding username fields to social accounts and adding Farcaster support. It also improves documentation clarity and adds sorting options for profile balances.

Key changes:
- Added `username` field to Instagram, TikTok, and Twitter social accounts
- Added Farcaster social account support with username and display name
- Added sorting options and exclude hidden parameter to profile balances
- Fixed a comment in the profile documentation (from "social links" to "linked wallets")
- Simplified navigation in docs by removing "Metadata Builder" link and renaming "Profile Queries" to "Profile"

## Motivation and Context

These enhancements provide more complete social account data for profiles, allowing applications to link directly to users' social media accounts. The addition of Farcaster support reflects the growing importance of this platform in the web3 space.

## Does this change the ABI/API?

- [x] This changes the ABI/API

This adds new fields to existing API responses but maintains backward compatibility.

## What tests did you add/modify to account for these changes

Manually verified that the new fields appear correctly in API responses and that documentation accurately reflects the available data.

## Types of changes

- [ ] Bug fix (non-breaking change which fixes an issue)
- [x] New module / feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

## Checklist:

- [x] My code follows the code style of this project.
- [x] My change requires a change to the documentation.
- [x] I have updated the documentation accordingly.
- [ ] I added a changeset to account for this change

## Reviewer Checklist:

- [ ] My review includes a symposis of the changes and potential issues
- [ ] The code style is enforced
- [ ] There are no risky / concerning changes / additions to the PR

Author: iainnash

docs/pages/coins/sdk/queries/profile.mdx

@@ -47,7 +47,7 @@ async function fetchUserProfile() {
       console.log("- Profile Image:", profile.avatar.medium);
     }
 
-    // Access social links if available
+    // Access linked wallets if available
     if (profile?.linkedWallets && profile?.linkedWallets?.edges?.length || 0 > 0) {
       console.log("Linked Wallets:");
       profile?.linkedWallets?.edges?.forEach((link: any) => {
@@ -93,20 +93,20 @@ type ProfileData = {
     };
     socialAccounts?: {        // Connected social accounts
       instagram?: {
-        username?: string;
-        displayName?: string;
+        username?: string;      // Instagram username
+        displayName?: string;   // Instagram display name
       };
       tiktok?: {
-        username?: string;
-        displayName?: string;
+        username?: string;      // TikTok username
+        displayName?: string;   // TikTok display name
       };
       twitter?: {
-        username?: string;
-        displayName?: string;
+        username?: string;      // Twitter/X username
+        displayName?: string;   // Twitter/X display name
       };
-      "farcaster": {
-        "username": "string";
-        "displayName": "string";
+      farcaster?: {
+        username?: string;      // Farcaster username
+        displayName?: string;   // Farcaster display name
       };
     };
     linkedWallets?: {         // Connected wallets

docs/vocs.config.ts

@@ -140,7 +140,7 @@ export default defineConfig({
                     link: "/coins/sdk/queries/coin",
                   },
                   {
-                    text: "Profile Queries",
+                    text: "Profile",
                     link: "/coins/sdk/queries/profile",
                   },
                   {

packages/coins-sdk/src/client/types.gen.ts

@@ -1552,10 +1552,6 @@ export type GetProfileResponses = {
            * The `String` scalar type represents textual data, represented as UTF-8 character sequences. The String type is most often used by GraphQL to represent free-form human-readable text.
            */
           displayName?: string;
-          /**
-           * The `String` scalar type represents textual data, represented as UTF-8 character sequences. The String type is most often used by GraphQL to represent free-form human-readable text.
-           */
-          id?: string;
         };
         farcaster?: {
           /**