Improve SDKAnalysisLevel guidance (#6989)

Author: nkolev92

docs/feature-guide.md

@@ -136,6 +136,16 @@ Therefore the following logic should apply anywhere NuGet needs to make a decisi
 This means that `SdkAnalysisLevel` is used as intended for SDK style projects, but non-SDK style project always use the latest defaults.
 All project types use the same configuration, so that customers can set a single property in a *Directory.Build.props* file, or environment variable.
 
+##### SDKAnalysisLevel and restore
+
+The SDKAnalysisLevel feature should be used with special care in features that ship simultaneously in .NET SDK and Visual Studio.
+For example, when running a restore on an .NET SDK project in Visual Studio, the Visual Studio shipped code and targets will be used. 
+When running a restore on the same project with the .NET CLI, the .NET SDK code will be used.
+
+Because of this, consider the [.NET SDK loading rules](https://learn.microsoft.com/en-us/dotnet/core/porting/versioning-sdk-msbuild-vs#targeting-and-support-rules).
+While Visual Studio 18.0, shipped with .NET 10.0.100 SDK, the minimum version for that .NET SDK is 17.14.
+What that means is that if a feature is available in the NuGet targets in 17.14, it will be enabled by default in 17.14, despite the fact that you may have only intended it to be enabled by default in .NET 10 only.
+
 #### Restore considerations
 
 * NuGet tool parity, ensure all products work as expected
@@ -150,6 +160,7 @@ All project types use the same configuration, so that customers can set a single
 * Performance considerations
   * How is incremental restore affected?
   * How is full restore affected?
+* Consider [SDKAnalysisLevel](#sdkanalysislevel-and-restore)
 
 #### Pack considerations