Title: Eclipse Console does not sync stdin/stdout correctly on Windows 11 (Eclipse 4.37.0)

Body:
I am experiencing an issue with the Eclipse Console when running Java programs that read user input using and . The console cursor does not move to the correct line before input is requested, even though the program prints newline characters and flushes the output stream.
The same code works correctly in a normal Windows terminal (CMD/PowerShell), so the problem appears to be specific to the Eclipse Console’s handling of stdout/stdin synchronization.
Environment:
• OS: Windows 11
• Eclipse IDE: 4.37.0
• Java: (any version, issue is reproducible across multiple JDKs)
Steps to reproduce:
1. Create a simple Java program that prints a line, flushes stdout, and then calls or similar.
2. Run the program in the Eclipse Console.
3. Observe that the cursor appears on the wrong line or overlaps previous output.
Expected behavior:
The cursor should appear on a new line exactly where the program prints the input prompt.
Actual behavior:
The cursor appears on the previous line or in an incorrect position, making interactive console programs difficult to use.
This issue seems related to how the Eclipse Console buffers and renders stdout before stdin is requested.
Thank you for looking into this.

Let's make sure issue is not already fixed in latest builds first.

- [ ] I verified I can reproduce this issue against [latest Integration Build of Eclipse SDK](https://download.eclipse.org/eclipse/downloads/)

## Steps to reproduce

From a fresh installation and clean workspace:

* **
* *<...setup environment>*

I tried

* **
* *<... trigger issue>*

I expected: **

But got: **

## Here is some relevant log output

From `/.metadata/.log`
```

```

## Tested under this environment:
* OS & version: ...
* Eclipse IDE/Platform version (as shown in *Help > About*): ...
* ...Anything else that can be useful...

## Community

- [ ] I understand reporting an issue to this OSS project does not mandate anyone to fix it. Other contributors may consider the issue, or not, at their own convenience. The most efficient way to get it fixed is that I fix it myself and contribute it back as a good quality patch to the project.