Simplifying TextAreaPrintStream in Luke

### Description

Hi,

I've been looking into how [`org.apache.lucene.luke.app.desktop.util.TextAreaPrintStream`](https://github.com/apache/lucene/blob/main/lucene/luke/src/java/org/apache/lucene/luke/app/desktop/util/TextAreaPrintStream.java) is used in Luke, and I think its usage and its implementation may be simplified.

- It is used in `OptimizeIndexDialogFactory.ListenerFunctions` and `CheckIndexDialogFactory.ListenerFunctions`, both in a try-catch.
Since `TextAreaPrintStream` is closable, my first suggestion would be to use try-with-resources instead at those locations.
- Since there is always a new instance of `TextAreaPrintStream` instance created at the aforementioned locations, and they are flushed afterwards, it seems unnecessary to store the `ByteArrayOutputStream baos` field and call .reset() at all, when the `TextAreaPrintStream` instances are not reused.

Let me know what you think.

Start by reading lucene/luke/src/java/org/apache/lucene/luke/app/desktop/util/TextAreaPrintStream.java and its uses in OptimizeIndexDialogFactory.ListenerFunctions and CheckIndexDialogFactory.ListenerFunctions. Verify the current flush and close behavior, then check the relevant Luke tests. Done means the two call sites use try-with-resources and TextAreaPrintStream no longer retains unnecessary reusable buffering state.

Written by the indexing model from the issue text.