Remove Thread Check for Prefork/Postpork

### Is your feature request related to a problem? Please describe.
I'm integrating Puma with gRPC and have encountered a [thread consistency validation](https://github.com/grpc/grpc/blob/989fed6181c0861861da11af25274b3bd21760ae/src/ruby/ext/grpc/rb_grpc.c#L380-L385) that occurs during prefork and postfork phases. I'm trying to understand the rationale behind this validation. I conducted load testing without this validation, and the application seemed to perform well.

This relates to the discussion in this thread: https://github.com/grpc/grpc/issues/8798#issuecomment-2429591619.

### Describe the solution you'd like
If removing this validation does not pose an operational risk, I propose eliminating it to ensure compatibility with Puma.

### Describe alternatives you've considered
Another approach would be to ensure that Puma forks using the same thread to satisfy the validation. However, the necessity of this thread check for fork safety is unclear to me.

### Additional context
n/a