OrganizationProfile.id incorrectly typed as nullable (number|null)

## Bug Frontend OrganizationProfile types id as number | null but the backend always returns a non-null int. ## Impact - Code using orgProfile.id as a route param, React key, or API call parameter must null-check unnecessarily - If the type is reused for create forms where id is absent, it should be a separate type ## Fix Change frontend type from id: number | null to id: number for the response type. ## Location - Frontend: features/organizations/api/organizations.profile.api.ts - Backend: app/schemas/organization.py — OrganizationProfile.id: int ## Found by API contract audit (2026-03-19)