Propagate package namespaces information to the restore command

[nkolev92]

Child of #10727.

Blocked on #10731

[nkolev92]

@kartheekp-ms

There's some extremely basic work that has been started here:

https://github.com/NuGet/NuGet.Client/compare/dev-feature-packageNamespaces...dev-nkolev92-addDataInRestoreRequest?expand=1.

Note that for this particular task, what is in the current branch might be sufficient.

How I'd expect this to go:

RestoreRequest has the namespaces configuration.

From there, the configuration might go into the RemoteWalkContext and/or flow into the https://github.com/NuGet/NuGet.Client/blob/dev/src/NuGet.Core/NuGet.Commands/RestoreCommand/ProjectRestoreCommand.cs.

The actual package probing happens in https://github.com/NuGet/NuGet.Client/blob/dev/src/NuGet.Core/NuGet.DependencyResolver.Core/ResolverUtility.cs.

So you'd need to make sure that all the calls for resolution:

• PackageDownload - https://github.com/NuGet/NuGet.Client/blob/17bc64685d0943a8b840aa5e18059fb402a47a8c/src/NuGet.Core/NuGet.Commands/RestoreCommand/ProjectRestoreCommand.cs#L225
• PackageReference - ends up in https://github.com/NuGet/NuGet.Client/blob/17bc64685d0943a8b840aa5e18059fb402a47a8c/src/NuGet.Core/NuGet.DependencyResolver.Core/ResolverUtility.cs#L21 through https://github.com/NuGet/NuGet.Client/blob/17bc64685d0943a8b840aa5e18059fb402a47a8c/src/NuGet.Core/NuGet.DependencyResolver.Core/Remote/RemoteDependencyWalker.cs#L125-L132.
  The RemtoeDependencyWalker takes a RemoteWalkContext, so it may be where this information is propagated.

Note that the resolver utility does a lot of caching based on a package id. Note that this caching should remain project level, to avoid potential polluting due to different configurations.