Improve SessionPoolExample by replacing unbounded fixed thread pool with bounded ThreadPoolExecutor

### Search before asking

- [x] I searched in the [issues](https://github.com/apache/iotdb/issues) and found nothing similar.

### Motivation

I am sometimes frustrated when using the IoTDB CLI because the output of certain commands is difficult to read when the result set is large. The CLI currently prints results in a plain format which may be harder to interpret for users analyzing time-series data interactively.

Improving the CLI output formatting (for example better alignment or optional table-style display) would improve usability, especially for users exploring IoTDB from the command line.

### Solution

One possible solution is to improve the CLI output formatting by introducing a table-style display for query results.

For example, results could be formatted with aligned columns and clearer separators so that timestamps and values are easier to read.

Additionally, an optional CLI flag (for example `--pretty`) could allow users to enable or disable enhanced formatting depending on their preference.

The implementation could be handled in the CLI output handling logic located in:

`iotdb-client/cli/src/main/java/org/apache/iotdb/cli`

### Alternatives

An alternative approach could be to keep the current output format but allow users to export query results directly to formats such as CSV or JSON for easier processing in external tools.

However, improving the CLI display would provide a better interactive experience directly within the terminal.

### Are you willing to submit a PR?

- [x] I'm willing to submit a PR!

Commencez par localiser SessionPoolExample et faire correspondre la modification demandée de thread-pool avec le corps de l’issue, qui traite à la place du formatage de la sortie CLI dans iotdb-client/cli/src/main/java/org/apache/iotdb/cli. Confirmez quelle portée est visée, puis identifiez les tests pertinents ou l’exemple exécutable ; le travail est terminé lorsque la modification sélectionnée est implémentée sans création illimitée de threads et que son comportement est vérifié.

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