fix: ts-proto snake_case to camelCase, Chat.gRPC.createRoom() empty id res field

[kon14]

This PR disables ts-proto's snake_case to camelCase conversions.
For whatever reason, ts-proto seems to match leading underscores as snake_case, even though they're technically not.

Example: message field _id would become Id
Besides being a nuisance, this resulted in generated types not really working as expected across server/client.
Eg: Chat module's createRoom was expected to return Id server-side and receive the same field client-side, but we actually received an empty string (default gRPC value) instead.

While at it, I also modified DeleteRoomRequests signature to also return _id (previously id as a workaround).
This should make the API consistent, while also matching the underlying db doc field naming.

The modifications in Chat's proto file are technically a breaking change, but I'm not denoting this via conventional commits as we're already in an alpha stage and the previous behavior was also sketchy at best.
At least node users of grpc-sdk should become aware of this following an SDK bump.

This change shouldn't break any in-code generated types usage as we only ever build internal Conduit protos + the official gRPC health check proto file, neither of which make use of snake_case naming.

I only slightly modified Authorization's nested Resource.Relation and Resource.Permission message types, removing the explicit underscore prefix (ts-proto doesn't use namespaces), which shouldn't really affect anything.
Relevant generated types are never explicitly referenced either anyway.

What kind of change does this PR introduce?

• Bugfix
• Feature
• Code style update
• Refactor
• Build-related changes
• Other (please describe)

Does this PR introduce a breaking change?

• Yes
• No

The PR fulfills these requirements:

• It's submitted to the main branch
• When resolving a specific issue, it's referenced in the PR's description (e.g. fix #xxx, where "xxx" is the issue number)