Check why Fable.Compiler didn't have a symbol package pushed

[MangelMaxime]

Description

When publishing Fable.Compiler there was a warning/error from NuGet that not symbol packages was pushed along side the standard package.

Is this something we should investigate? If not, is there a way to tell NuGet to not emit a warning because of the missing symbol package?

@nojaf @baronfel

[nojaf]

The symbols are embedded for Fable.Compiler, so this is not super unlogical that no *.snupkg is present. Maybe all we need here is to add --no-symbols to the dotnet nuget push command.

[MangelMaxime]

I updated the build system to include --no-symbols.

I could not test this change because I already published the package without that. We will need to wait the next release to check if that solves the issue or not.