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

issue #5895 と PR #8452 から始め、提案されている ServerCallStreamObserver.setOnFinishHandler(...) API と、代替名についての議論を確認してください。実験的 API の最終的な命名とステータスを確認し、リンクされた作業によって未解決の判断またはフォローアップが残る場合にのみ、この追跡 issue を更新してください。

索引モデルが issue の本文から書いたものです。