Reported incompatibility with GNU Octave

The [GNU Octave](octave.org) is a cross platform project built to use the default OS terminal. Currently we would love to be able to identify if that is the new Windows Terminal. [There is some incompatibility between conhost and the new Windows Terminal](https://savannah.gnu.org/bugs/index.php?63430) that is [causing](https://savannah.gnu.org/bugs/index.php?63430) [strange](https://stackoverflow.com/questions/77490853/octave-showing-weird-output-and-command-window-not-working/77694207) [artifacts](https://stackoverflow.com/questions/77614821/octaves-comand-window-glitches-when-i-run-a-script/77620351) and [program](https://octave.discourse.group/t/octave-crashing-with-weird-characters-and-not-loading/) [crashes](https://stackoverflow.com/questions/77474803/octave-crashes-running-a-script-that-used-to-run-with-no-issues/77578495) for users of the new Windows Terminal that became very apparent when win11 made it the default. Octave is primarily developed on linux and crossbuilt for windows users, and we have few windows developers working that part of the program.

For now we wanted to create a script to try to identify if Octave was started in the Windows Terminal to prompt the user to switch, but so far have just settled on checking if the the registry key was set for having Windows Console Host be system default, and[ prompt the Windows users to switch the system default to that if it's not](https://octave.discourse.group/t/workaround-for-weird-behavior-of-command-window-widget-in-windows/4981). Yes, it is a rather poor workaround. but it's effective. Until we have the developer resources to better troubleshoot the conhost / windows terminal incompatibility (or finish developing a separate, cross-platform compatible terminal widget to bundle with Octave), that change solves the problem for the users. But it does come with some false positives for the prompt because it gets set off when the windows setting is "let windows decide" even if that wouldn't use the new terminal, causing some other user confusion. So, it would at least be cleaner if at startup we could positively identify the Windows terminal.

_Originally posted by @NRJank in https://github.com/microsoft/terminal/issues/7434#issuecomment-2050836000_

No source files or tests are named in the issue. Start by tracing Windows Terminal startup handling and the existing registry-based console-host workaround, then determine where positive terminal identification belongs; done means startup can distinguish Windows Terminal from conhost and avoid the workaround's false-positive prompt.

Written by the indexing model from the issue text.