adding stream interceptor for logging middleware

[akoserwal]

Description (what this PR does / why we need it):

Update the stream interceptor to handle stream use-case

Which issue(s) this PR fixes (resolves / be part of):

fixes #3351

Other special notes for the reviewers:

[xuyang2]

似乎可以直接用 "github.com/grpc-ecosystem/go-grpc-middleware/v2/interceptors/logging"

• https://pkg.go.dev/github.com/grpc-ecosystem/go-grpc-middleware/v2/interceptors/logging
• https://github.com/grpc-ecosystem/go-grpc-middleware/tree/main/interceptors/logging/examples
• https://github.com/grpc-ecosystem/go-grpc-middleware/tree/main/interceptors/logging

或者复用 interceptors.StreamServerInterceptor()
只用实现一个 ServerReportable 接口

[akoserwal]

It seems that you can use it directly"github.com/grpc-ecosystem/go-grpc-middleware/v2/interceptors/logging"

• https://pkg.go.dev/github.com/grpc-ecosystem/go-grpc-middleware/v2/interceptors/logging
• https://github.com/grpc-ecosystem/go-grpc-middleware/tree/main/interceptors/logging/examples
• https://github.com/grpc-ecosystem/go-grpc-middleware/tree/main/interceptors/logging

Using the above can cause conflict between using kratos middleware for unary and using grpc-middleware for stream server

Does the above apply to all the middlewares: auth, circuit breaker, metadata, metrics, rate limit, recovery, selector, tracing, validate etc?

[akoserwal]

@shenqidebaozi I updated the PR to have a middleware abstraction for the streaming middleware. grpc-gateway middleware also configure the unary and stream as separate interceptors configs
https://github.com/grpc-ecosystem/go-grpc-middleware/blob/main/examples/server/main.go#L136

[akoserwal]

@go-kratos/contributor please take a look and provide feedback. Another proposal to unify the unary and stream interface: akoserwal#1

[shenqidebaozi]

ok， Let's discuss this design

[akoserwal]

@shenqidebaozi updated the interceptor based on your suggestions

[akoserwal]

@shenqidebaozi Is there anything remaining? please take a look

[shenqidebaozi]

@akoserwal I think it's ready now, but I need to test it again