Use DECCRA/DECFRA for ScrollConsoleScreenBuffer (#17747)

This adds logic to get the DA1 report from the hosting terminal on
startup. We then use the information to figure out if it supports
rectangular area operations. If so, we can use DECCRA/DECFRA to
implement ScrollConsoleScreenBuffer.

This additionally changes `ScrollConsoleScreenBuffer` to always
forbid control characters as the fill character, even in conhost
(via `VtIo::SanitizeUCS2`). My hope is that this makes the API
more consistent and robust as it avoids another source for
invisible control characters in the text buffer.

Part of #17643

## Validation Steps Performed
* New tests ✅

tools/OpenConsole.psm1

@@ -169,7 +169,7 @@ function Invoke-OpenConsoleTests()
         [switch]$FTOnly,
 
         [parameter(Mandatory=$false)]
-        [ValidateSet('host', 'interactivityWin32', 'terminal', 'adapter', 'feature', 'uia', 'textbuffer', 'til', 'types', 'terminalCore', 'terminalApp', 'localTerminalApp', 'unitSettingsModel', 'unitRemoting', 'unitControl')]
+        [ValidateSet('host', 'interactivityWin32', 'terminal', 'adapter', 'feature', 'uia', 'textbuffer', 'til', 'types', 'terminalCore', 'terminalApp', 'localTerminalApp', 'unitSettingsModel', 'unitRemoting', 'unitControl', 'winconpty')]
         [string]$Test,
 
         [parameter(Mandatory=$false)]

tools/tests.xml

@@ -15,4 +15,5 @@
   <test name="til" type="unit" binary="til.unit.tests.dll" />
   <test name="feature" type="ft" binary="Conhost.Feature.Tests.dll" />
   <test name="uia" type="ft" binary="Conhost.UIA.Tests.dll" />
+  <test name="winconpty" type="ft" binary="winconpty.Feature.Tests.dll" />
 </tests>