Add new SYSLIB warnings

[gewarren]

Update this page based on https://github.com/dotnet/runtime/blob/main/docs/project/list-of-diagnostics.md.

• SYSLIB0003 - see https://github.com/dotnet/runtime/pull/57035/files
• SYSLIB0013
• SYSLIB0014
• SYSLIB0015
• SYSLIB0016
• SYSLIB0017 - see https://github.com/dotnet/runtime/pull/50941/files
• SYSLIB0018 - see https://github.com/dotnet/runtime/pull/50941/files
• SYSLIB0019
• SYSLIB0020
• SYSLIB0021 - see https://github.com/dotnet/runtime/pull/52303/files
• SYSLIB0022 - see https://github.com/dotnet/runtime/pull/52366/files
• SYSLIB0023 - see https://github.com/dotnet/runtime/pull/52373/files
• SYSLIB0024 - see https://github.com/dotnet/runtime/pull/52014/files
  • This PR also adds new obsoletion attributes using SYSLIB003 and SYSLIB0011
• SYSLIB0025 - see https://github.com/dotnet/runtime/pull/50951/files
• SYSLIB0026 - see https://github.com/dotnet/runtime/pull/53891/files
• SYSLIB0027 - see https://github.com/dotnet/runtime/pull/54562/files
• SYSLIB0028 - see https://github.com/dotnet/runtime/pull/54562/files
• SYSLIB0029 - see https://github.com/dotnet/runtime/pull/54886/files
• SYSLIB0030 - see https://github.com/dotnet/runtime/pull/54886/files
• SYSLIB0031 - see https://github.com/dotnet/runtime/pull/55592/files
• SYSLIB0032 - see https://github.com/dotnet/runtime/pull/56664/files
• SYSLIB0033 - see https://github.com/dotnet/runtime/pull/57002/files
• SYSLIB0034 - see https://github.com/dotnet/runtime/pull/57301/files
• SYSLIB0035 - see https://github.com/dotnet/runtime/pull/57301/files

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 48bcb45e-7c1e-8c8e-cf73-3a4afb71ec62
• Version Independent ID: c4971f9b-4496-dfa5-8c88-f09daff995b8
• Content: Obsolete features in .NET 5+ - .NET
• Content Source: docs/core/compatibility/syslib-obsoletions.md
• Product: dotnet-fundamentals
• GitHub Login: @gewarren
• Microsoft Alias: gewarren

[jeffhandley]

@gewarren I want to confirm that you plan to review the list-of-diagnostics.md file and gather all of the new diagnostics from there to produce the breaking change document, and that (so long as we accumulate the diagnostics there) we do not need to submit separate issues for each new obsoletion. Is that correct?

If that's the case, would it still be helpful for us to link to this issue from each PR that introduces a diagnostic?

[gewarren]

@jeffhandley Yes, that's correct, and you don't need to submit separate issues. But I think it would be helpful to link to this issue from the PRs, as a sign that there's a new one to add to the breaking changes doc. Thanks!