[FlightRPC][Integration] Ensure all RPC methods are covered by integration testing

This would help catch issues like https://github.com/apache/arrow/issues/13853

**Reporter**: [David Li](https://issues.apache.org/jira/browse/ARROW-17568) / @lidavidm
#### Related issues:
- [[Flight] Test Flight servers and clients with a generic gRPC services](https://github.com/apache/arrow/issues/20981) (relates to)

_{**Note**: *This issue was originally created as [ARROW-17568](https://issues.apache.org/jira/browse/ARROW-17568). Please see the [migration documentation](https://github.com/apache/arrow/issues/14542) for further details.*}

首先找到現有的 FlightRPC 整合測試，並列出 Java 實作公開的 RPC 方法。比較這兩組方法，然後為缺少的方法新增涵蓋；當每個 RPC 方法都由整合測試執行，且能偵測到如所連結的 Arrow 13853 案例這類問題時，即表示完成。

由索引模型根據 Issue 內容生成。