It's the developer's responsibility to deal with the server-side timeout. If you ignore the context's deadline, go won't complain about it.
Client-side timeout won't be ignored, but the developer can choose to time out early.
Client-side timeout can't be set with gRPC metadata, becasue grpc-timeout information is within the HTTP2 Request-Headers frame.