Remove internal-only methods from testing package

As mentioned in comments in #3099, there are some issues and limitation to the current unit test tools:

- It's hard to test a user-defined generic interceptor.
- People are abusing `NoopClientCall`, using it as an alternative of `mock(ClientCall.class)`, which is as bad as a mock.
- `TestMethodDescriptors.noopMarshaller` does not gain much benefit. It violates the interface's contract, it's equivalent to a `mock(Marshaller.class)`, and it does not work in InProcess transport or interop test.

Examinez les utilisations de NoopClientCall et de TestMethodDescriptors.noopMarshaller dans le package de testing, ainsi que la discussion dans #3099. Identifiez les helpers à usage interne uniquement concernés par l’issue et leurs callers affectés ; le travail est terminé lorsque ces helpers n’encouragent plus les patterns de testing listés sans casser les outils de testing.

Rédigé par le modèle d'indexation à partir du texte de l'issue.