fix: move account struct to app-server-protocol and use camelCase

[owenlin0]

Makes sense to move this struct to app-server-protocol/ since we want to serialize as camelCase, but we don't for structs defined in protocol/

It was:

export type Account = { "type": "ApiKey", api_key: string, } | { "type": "chatgpt", email: string | null, plan_type: PlanType, };

But we want:

export type Account = { "type": "apiKey", apiKey: string, } | { "type": "chatgpt", email: string | null, planType: PlanType, };

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[chatgpt-codex-connector]

Use camelCase for Account payload fields

The new Account enum is intended to serialize as camelCase, but the fields api_key and plan_type remain in snake_case. #[serde(rename_all = "camelCase")] on the enum only affects variant names, so JSON and ts-rs output will still be { "type": "apiKey", "api_key": … } and { "type": "chatgpt", "plan_type": … }, which contradicts the stated goal of producing apiKey/planType. Any client updated to expect camelCase properties will fail to deserialize these messages. Rename the fields or add per-field/variant serde and ts renames to produce camelCase.

Useful? React with 👍 / 👎.

[bolinfest]

@owenlin0 can you verify this?

[owenlin0]

codex is right, updated and added a quick test to verify