[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 内容生成。