[Group 5] Enable nullable annotations for System.Security.Cryptography.Xml

[SteveDunn]

This is a pre-requisite for nullable annotations to Microsoft.Extensions.Configuration.Xm as described in Annotate Microsoft.Extensions.* assemblies for nullable reference types

[ghost]

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

Issue Details

---

This is a pre-requisite for nullable annotations to Microsoft.Extensions.Configuration.Xm as described in Annotate Microsoft.Extensions.* assemblies for nullable reference types

Author:	SteveDunn
Assignees:	-
Labels:	area-Meta, untriaged
Milestone:	-

[ghost]

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

Issue Details

---

This is a pre-requisite for nullable annotations to Microsoft.Extensions.Configuration.Xm as described in Annotate Microsoft.Extensions.* assemblies for nullable reference types

Author:	SteveDunn
Assignees:	-
Labels:	area-System.Security, untriaged, in-pr
Milestone:	-

[jeffhandley]

@krwq The relationship between this issue/PR and #73687 was unclear to me. I'm going to go ahead and move this issue to 8.0.0, but here's what I recommend:

1. If Nullable annotations for System.Security.Cryptography.Xml #67198 gets merged in before the .NET 7 RC 1 snap on Monday, that will be nice! We can change this issue milestone back to 7.0.0.
2. If not, but it gets merged in next week, we can consider requesting for it to be ported into the RC1 branch (and announce it as a breaking change if necessary).
3. Otherwise, it will be part of .NET 8; I wouldn't want to introduce it in RC2.

[krwq]

8.0.0 is fine. The issue I fixed was found while adding annotations to S.S.C.Xml and made it confusing to annote that's the only relationship