Tracking Issue for setOnCloseHandler being Experimental

To resolve issue #5895 PR #8452 has been created that adds new `ServerCallStreamObserver.setOnFinishHandler(...)` method.
The handler is called by `Listener.onComplete` _when the call is **finished** correctly from the server's point of view: either `onCompleted()` or `onError(Throwable)` has been called, all the messages and trailing metadata have been put on the wire and the stream has been closed_.

Several names were proposed for the handler:
- `onCompleteHandler` : derives name from `Listener`'s method but causes confusion with `StreamObserver.onCompleted()`
- `onSuccessHandler` : my initial idea, yet also confusing as it can be called also after `StreamObserver.onError(...)`
- `onFinishHandler` : current approach, matches well the verb from method's javadoc
- `onFinalizeHandler` : would also probably do well

Commencez par l’issue #5895 et la PR #8452, puis examinez l’API proposée ServerCallStreamObserver.setOnFinishHandler(...) et sa discussion sur les noms alternatifs. Confirmez le nom final et le statut de l’API expérimentale, et mettez à jour cette issue de suivi uniquement si le travail lié laisse une décision ou une action de suivi en suspens.

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