Add comment for coordinating with other .NET repos for relevant deps

[aortiz-msft]

Description

As a follow up to dotnet/sdk#43339, add a comment for coordinating with other .NET repos for relevant dependencies:

1. msbuild assemblies
2. System.Text.Json
3. System.Collections.Immutable
4. System.Reflection.Metadata
5. System.Reflection.MetadataLoadContext

PR Checklist

• Meaningful title, helpful description and a linked NuGet/Home issue
• Added tests - N/A
• Link to an issue or pull request to update docs if this PR changes settings, environment variables, new feature, etc. - N/A

[kartheekp-ms]

At a quick glance, I was unable to identify the changes proposed in this pull request. Therefore, I am adding this review comment to help team members understand the proposed changes. In summary, the <!-- Do not update the version of System.Text.Json without explicit approval from the .NET SDK and .NET MsBuild repo owners. --> comment has been added in this PR.

[donnie-msft]

Thanks, Kartheek. Why is this document completely modified? Was the indentation wrong before, or is it wrong now?

Please try reverting and just adding the comment to minimize the change.

[aortiz-msft]

Weird... I used GitHub Web Editor, which shows the expected diff. However, GitHub itself shows that the entire file changed.

[zivkan]

Pressing . on github on this PR opens https://github.dev/NuGet/NuGet.Client/pull/6024.
From there, opening Directory.Packages.props, vscode shows at the bottom of the screen: UTF-8 CRLF.

Editing the URL to https://github.dev/NuGet/NuGet.Client/ and again opening Directory.Packages.props, it now says UTF-8 LF

So, github changed every line ending from LF to CRLF. It did the wrong thing:

NuGet.Client/.gitattributes

Lines 1 to 2 in 785d8bb

	# Auto detect text files and perform LF normalization
	* text=auto

For what it's worth, I'm preparing a branch that will split package versions depending if the project inserts into the .NET SDK or not, because for some packages, it's necessary due to the VS SDK to avoid package downgrade warnings. I'll be adding comments similar to what I added in this release-6.11.x fix: https://github.com/NuGet/NuGet.Client/pull/6015/files

[aortiz-msft]

Codeflow also shows the expected diff and shows no whitespace changes.

[zivkan]

actually, github did not do the wrong thing, the dev branch has the wrong line endings

NuGet.Client/.gitattributes

Line 62 in 785d8bb

*.props text eol=crlf

[aortiz-msft]

Unless I hear otherwise, I'm going to send a PR just to update to CRLF, then rebase this branch against that.

[dotnet-policy-service]

This PR has been automatically marked as stale because it has no activity for 7 days. It will be closed if no further activity occurs within another 7 days of this comment. If it is closed, you may reopen it anytime when you're ready again, as long as you don't delete the branch.

[KirillOsenkov]

Did this get lost?

[aortiz-msft]

Did this get lost?

Yeah. Whitespace handling by the tooling is making it too hard to rebase this PR, so I just created a new one: https://github.com/NuGet/NuGet.Client/pull/6112/files