Improve package publish logic

[lahma]

• include release* branches
• read version from branch name if starts with release
• change output from artifacts to publish (artifacts will be used by NET 8 for binaries)

As i used release1.5.1 (an imaginary version) as my branch name, you can see that the build on my fork determined this to be publish build and forced all version information from the branch name, output from ubuntu-latest run:

06:13:26 [INF] BUILD SETUP
06:13:26 [INF] 	Solution: /home/runner/work/npoi/npoi/solution/NPOI.Core.Test.sln
06:13:26 [INF] 	Configuration: Release
06:13:26 [INF] 	Version suffix: 
06:13:26 [INF] 	Publish version: 1.5.1
06:13:26 [INF] Build environment:
06:13:26 [INF] 	Host: Nuke.Common.CI.GitHubActions.GitHubActions

The summary has the Artifacts at the bottom https://github.com/lahma/npoi/actions/runs/5983250670 which opens a zip file containing a NuGet package versioned as 1.5.1 and passes all NuGet checks:

So with these changes you should be able to get NuGet release branch from any release branch automatically as long as branch name starts with release.

[tonyqus]

LGTM

[tonyqus]

The CI works great! It's really a life saver. Thank you!

I'm impressed that it can even automatically update dependency packages for the nuget package.

[lahma]

So nice to hear! When it's scripted and automated, it's usually reproducible and and has expect results (release build, exactly known sources etc).