Improve packaging procedures

[lahma]

fixes #1076

• add standard Apache-2.0 license expression which will be shown on nuget.org
• add VersionPrefix so that build artifact will have proper package version instead of default 1.0.0
• add AllowedOutputExtensionsInPackageBuildOutputFolder to have PDBs like they seem to be on NuGet org package
• add missing properties that are present in nuget.org package
• add logos, readme and license into package the say way they are in nuget.org package
• remove NUKE build project configurations from solution

If you open the package with NuGet Package Explorer from online feed you can see there are couple problems:

These should be OK if build artifact from GitHub build pipeline is used - it has the flags set. So I believe the current release in NuGet is also unoptimized (Debug build).

[lahma]

Now when I download the artifacts from this PRs run summary https://github.com/nissl-lab/npoi/actions/runs/5234208516 artifacts section and open, extract the two files (NPOI.2.6.1.nupkg, NPOI.2.6.1.snupkg) to folder and open with NuGet Package Explorer, all checks are green:

So the VersionPrefix determines the version for packaging and these two files should be uploaded to nuget.org for each release (from master branch build). Of course it would be nice to have package version to be determined by Git tag and automatic push to nuget.org like Quartz does, but that's another story.

[tonyqus]

LGTM

[tonyqus]

I double check the nuget packages generated by artifacts.

DLLs for NPOi.OOXML, NPOI.OpenXmlFormats, NPOI.OpenXMLNet are missing in the package.

[lahma]

@tonyqus can you share how you created the NuGet package so I can trace steps how to ensure pipeline produces the same?

[tonyqus]

It's just manual work. I created the nuget package usually by copying from the old version of nuget packages. For example, NPOI 2.6.1.nupkg is copied from NPOI 2.6.0 package. And I remove all the old DLLs from the package and replace them with the new one.