[FlightRPC][FlightSQL][Java] Make FlightSqlClientDemo a general purpose tool

The FlightSqlClientDemo test program has a limited set of options that prevents it from being used against production databases. It does work against the Derby and SQLite examples though.

The major limitation is that there is no way to supply authentication information. The proposal here is to add support for passing in HTTP basic credentials and Authorization: Bearer headers.

Another useful feature would be an option to supply arbitrary headers (as a way of support server-specific options).

Lastly, it would be good to add an interactive mode that just ran the tool in a loop based on user input (and use ClientCookieMiddleware in this mode to persist state).

A shaded configuration of the flight-sql module that set this tool's main function as the JAR entry point would make it more friendly to run as well.

This would make the tool comparable to SQLLine.

**Reporter**: [James Duong](https://issues.apache.org/jira/browse/ARROW-15843) / @jduo

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

Commencez par localiser le programme de test FlightSqlClientDemo et la configuration du module flight-sql. Examinez comment ClientCookieMiddleware pourrait prendre en charge le mode interactif proposé, puis définissez le périmètre des identifiants, des en-têtes bearer et arbitraires, de l’exécution interactive et du point d’entrée du shaded JAR. Le travail est terminé lorsque l’outil prend en charge les options sélectionnées et peut être exécuté facilement sur des bases de données de production.

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