[Server] organizationWithUserRoles.id returns zero UUID in organization users response

00000000-0000-0000-0000-000000000000

For example, when requesting users for an organization, the response
contains entries such as:

{
  "userId": "...",
  "email": "...",
  "organizationWithUserRoles": {
    "id": "00000000-0000-0000-0000-000000000000",
    "roleNames": ["organization admin"]
  }
}

The requested organization has a real organization ID, but the nested
organizationWithUserRoles.id does not reflect it.

### Expected Behavior

organizationWithUserRoles.id should contain the ID of the organization
associated with the returned user-role relationship rather than the zero UUID.

### Screenshots/Logs

Observed against the deployed Meshery Cloud API using an authenticated test
account.

The users and their role names are returned correctly, and organization
scoping is otherwise working as expected.

### Environment
Host OS: Linux
Platform: Meshery Cloud
Meshery Server Version: Cloud deployment
Meshery Client Version: N/A
### To Reproduce
Authenticate to Meshery Cloud.
Send:
GET /api/identity/orgs/{orgId}/users
Inspect the organizationWithUserRoles object in the returned users.
Observe that organizationWithUserRoles.id is:
00000000-0000-0000-0000-000000000000

instead of the organization ID associated with the request.

### Additional Context

The roleNames values are populated correctly, and the endpoint respects
organization scoping. This appears to be a response-model or serialization
issue rather than an authorization issue.

I would be interested in working on this issue and submitting a fix if it is
confirmed. Please assign it to me if it is available.