consolidate SslStream to single file

[wfurt]

This was suggested by @stephentoub on #68678. The current split is somewhat artificial because of historical reasons.
There are two challenges:

• preserving history & blame. That should be possible AFAIK but it should be tested.
• We will need to make some bigger refactor of UnitTests. They link SslStream.cs now and that have fakes for the rest. We would either need to compile some parts conditionally, refactor the tests of find some other way how to get similar functionality.

We may also add section tags so at least in VS related sections are collapsible.

Tagging subscribers to this area: @dotnet/ncl, @vcsjones
See info in area-owners.md if you want to be subscribed.

Issue Details

---

This was suggested by @stephentoub on #68678. The current split is somewhat artificial because of historical reasons.
There are two challenges:

• preserving history & blame. That should be possible AFAIK but it should be tested.
• We will need to make some bigger refactor of UnitTests. They link SslStream.cs now and that have fakes for the rest. We would either need to compile some parts conditionally, refactor the tests of find some other way how to get similar functionality.

We may also add section tags so at least in VS related sections are collapsible.

Author:	wfurt
Assignees:	-
Labels:	area-System.Net.Security
Milestone:	Future

[stephentoub]

preserving history & blame

This isn't being negatively impacted by your current PR?

[wfurt]

Blame works because with git move it is essentially still the same file. History does not seems to. Maybe something we can still fix.

[rzikm]

History does not seems to. Maybe something we can still fix.

Did you try the --follow parameter?

--follow
Continue listing the history of a file beyond renames (works only for a single file).

$ git log --follow --pretty=oneline things/text.txt
8567d... Move file into things directory
1458a... Fix something
0aac5... Add something

[wfurt]

No. I was using GitHub UI. I know we had some tooling to replay history when we moved to new repo. Perhaps @ViktorHofer has some more insight.

[ViktorHofer]

Rewriting history requires to force push a branch and we obviously can't do that anymore. git log --follow usually works fine for these kinds of changes.

[rzikm]

We don't want to lose access to git blame on the individual files, so we will not be consolidating the source files.