Is your feature request related to a problem? Please describe

Currently, gRPC API allows to set a global error_trace parameter on gRPC requests that enables/disables detailed error tracing (see API parameter here).

To be compatible with the REST interface, the server side flag to enable/disable detailed error tracing is missing. See the corresponding flag here.

Describe the solution you'd like

It was identified in the scope of #19092 that having similar flag for gRPC APIs would allow to have the same semantics, while using the global error_trace parameter.

Such parameter can be called grpc.detailed_errors.enabled.

Related component

Other

Describe alternatives you've considered

One of the options is not to add the setting at all but it would leave the server with no control over the error traces which might cause some security-related concerns see: #4255.

Another option to rely on (http.detailed_errors.enabled)[https://docs.opensearch.org/latest/install-and-configure/configuring-opensearch/network-settings/#http-error-handling-settings] but it is defined for the separate interface and having an independent setting would allow for better scoping and greater flexibility.

Additional context

No response