feat(grpc): introduce Status and ServerStatus types

[sauravzg]

Introduces the foundational Status and ServerStatus types for gRPC status handling.

• Status: Represents a standard gRPC status with a code and message.
• ServerStatus: A wrapper around Status designed to prevent accidental leakage of sensitive server errors to the client. This type distinction ensures that handlers must explicitly convert to Status, encouraging a conscious decision about what information is exposed.
• StatusCode: Enum representing standard gRPC status codes.

This implementation provides the necessary types to unblock server-side API development without relying on a heavy tonic::Status. This is not meant to be an intermediate or final Status implementation but serves as a way to implement functional requirements while we design the final Status.

[darth-raijin]

I left one suggestion on the tests about avoiding duplication of the "ok" message by assigning it to a variable and reusing it in the assertions. It should make the test a bit less brittle if the message ever changes.

[dfawley]

This is fine, but I do think we should strongly consider aligning a little more with the internal design for Status, particularly having a StatusError type that can't represent OK, and a Status that is Result<(), StatusError> for now. That might help prevent future misconceptions/etc.

[sauravzg]

Noted. I have unfortunately progressed a lot on my branch. So, I'll take it as a todo and migrate all code to use a Status like approach in a future change.