Push with --no-symbols should also not push symbols.nupkg

[CoskunSunali]

Details about Problem

The command dotnet nuget push works as expected but reports wrong output.

dotnet.exe --info:

.NET Command Line Tools (2.0.0-preview1-005977)

Product Information:
Version: 2.0.0-preview1-005977
Commit SHA-1 hash: 414cab8a0b

Runtime Environment:
OS Name: Windows
OS Version: 10.0.15063
OS Platform: Windows
RID: win10-x64
Base Path: C:\Program Files\dotnet\sdk\2.0.0-preview1-005977\

Microsoft .NET Core Shared Framework Host

Version : 2.0.0-preview1-002111-00
Build : 1ff021936263d492539399688f46fd3827169983

Detailed repro steps so we can see the same problem

1. Execute dotnet pack command with --include-symbols option.
2. Execute dotnet nuget push command with --no-symbols option (symbol packages created with the dotnet pack command are being pushed to a symbol server rather than the package server).
3. The following result is generated reading that symbol package is pushed (partially copied here)

info : Pushing xyz.0.1.0-alpha.symbols.nupkg to 'https://www.myget.org/F/FeedName/api/v2/package'...
info :   PUT https://www.myget.org/F/FeedName/api/v2/package/
info :   Created https://www.myget.org/F/FeedName/api/v2/package/ 335ms
info : Your package was pushed.

4. The symbol packages are actually never pushed which is the correct behavior. It is just the information message display is wrong.
   ...

[donnie-msft]

@rrelyea Push does try to pushing symbols.nupkgs even with this switch. The switch only disables .snupkgs. Is this an issue or by design? If the latter, then maybe simply clarifying the docs/help messages would be helpful.

Repro'd with 5.5.0 preview 1.