Better differentiate packages for grpc-dotnet from deprecated grpc

Can we use a separate icon for grpc-dotnet related packages when publishing to NuGet?
It would be great, if the packages that are related to grpc-dotnet are better distinguishable from the grpc packages. This may reduce a lot of confusion, questions and issues from users, that somehow incorrectly mix the two code lines together.

Start by reviewing how grpc-dotnet packages are published to NuGet and where their package metadata and icon are defined. Update the related package branding so grpc-dotnet packages are distinguishable from deprecated grpc packages, then verify the published metadata and icon for the affected packages.

Written by the indexing model from the issue text.