[FlightRPC] Bearer Token refresh design with retry mechanism

- The generated bearer token by implementations of CallHeaderAuthenticator such as BearerTokenAuthenticator are bound to expire.
- The expired access token needs to be refreshed.
- The FlightClient needs to retry the API call on encountering FlightStatusCode.TOKEN_EXPIRED and refresh the expired token.

Refer to this [design document](https://docs.google.com/document/d/187DlGpIpOUPGhWvXVQEq0mXw_hdWjzzOuZp0p5qzBp0/edit?usp=sharing) for more details.

**Reporter**: [Keerat Singh](https://issues.apache.org/jira/browse/ARROW-10671)
#### PRs and other links:
- [GitHub Pull Request apache/arrow#8780](https://github.com/apache/arrow/pull/8780)

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

まず FlightClient と CallHeaderAuthenticator の実装（BearerTokenAuthenticator を含む）から始め、次にリンクされた設計ドキュメントと pull request #8780 を確認します。期限切れトークンによるレスポンスでトークンの更新が実行され、FlightClient が仕様どおり API 呼び出しを再試行すれば完了です。

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