Registry server does not apply error conversion with no_auth setting #4542

Expected Behavior

When a Registry Server is launched with no_auth setting, the remote client proxy must receive the same original error as generated on the server-side.

Current Behavior

The clients receives an _InactiveRpcError instead.

Steps to reproduce

• Launch a registry server with no_auth setting.
• From a remote client invoke a method that raises an error, e.g. store.list_entities('invalid_name')

Possible Solution

The interceptor must be added with any auth setting.