Add a client IP column to the login history table (backend #13941)

The backend now records \`client_ip\` on login history and audit log entries and adds a \`client_ip_masking_policies\` admin policy (lablup/backend.ai#13941). The WebUI login history table needs to be updated to surface this data.

## Scope

- Add a **Client IP** column to the login history table (\`BAILoginHistoryTable\` / \`LoginHistory\`), reading the new \`client_ip\` field from the GraphQL schema.
- Respect the masking policy: render the value the server returns (masked or full) as-is; do not attempt to unmask or reformat on the client.
- Update the related audit-log presentation where the same field applies (\`BAIAuditLogNodes\`, \`BAIAuditLogStatusTag\`) and the user settings login history view (\`UserSettingsPage\`).
- Update \`data/schema.graphql\`, the Relay fragments, and i18n keys for the new column header.

## Out of scope

- The admin UI for managing \`client_ip_masking_policies\` (separate issue).

—

Captured while working on branch: FR-3558-e2e

JIRA Issue: FR-3661

Start with BAILoginHistoryTable and LoginHistory, then trace the Relay fragments and data/schema.graphql definitions for login history. Update the related BAIAuditLogNodes, BAIAuditLogStatusTag, UserSettingsPage, and i18n keys so the server-returned client_ip is displayed as-is in the login history and audit-log views.

Written by the indexing model from the issue text.