Console.Unix: revert SetWindowSize implementation.

[tmds]

SetWindowSize was implemented using using TIOCSWINSZ.
TIOCSWINSZ is meant to inform the kernel of the terminal size.
The window that shows the terminal doesn't change to match that size.

Fixes #96208.

@dotnet/area-system-console ptal.

[dotnet-issue-labeler]

Note regarding the new-api-needs-documentation label:

This serves as a reminder for when your PR is modifying a ref *.cs file and adding/modifying public APIs, please make sure the API implementation in the src *.cs file is documented with triple slash comments, so the PR reviewers can sign off that change.

[tmds]

@stephentoub do you have additional feedback?

[stephentoub]

@dotnet/area-system-console, can you please review, in particular for the concept of the change?

[tmds]

@dotnet/area-system-console is this good to merge?

[tmds]

@adamsitnik ptal.

[jeffhandley]

@jozkee Please review this. We should get this into RC1.

[jozkee]

How was this generated? I tried as described in #75824 (comment) but didn't get any changes related to Console.
cc @ericstj

[jozkee]

@ViktorHofer

[ericstj]

dotnet.cmd src/libraries/apicompat --no-dependencies /p:ApiCompatGenerateSuppressionFile=true should work, make sure you've built libs before doing that.

I think the comment you linked to had a different property name. The one listed in the error message and shared here should be the right one: ApiCompatGenerateSuppressionFile
https://learn.microsoft.com/en-us/dotnet/core/project-sdk/msbuild-props#apicompatgeneratesuppressionfile

[ericstj]

Also these are all CP0014 - they are what I'd expect for the attribute changes to the reference assembly. If you're OK with those changes then these are fine (so long as build passes they are in sync).

[jozkee]

Thanks for checking them out. Btw, this is what I get from running dotnet.cmd:

C:\git\runtime>dotnet.cmd src\libraries\apicompat --no-dependencies /p:ApiCompatGenerateSuppressionFile=true
C:\Program Files\dotnet
Could not execute because the specified command or file was not found.
Possible reasons for this include:
  * You misspelled a built-in dotnet command.
  * You intended to execute a .NET program, but dotnet-src\libraries\apicompat does not exist.
  * You intended to run a global tool, but a dotnet-prefixed executable with this name could not be found on the PATH.