Add GitHub actions

[Toxantron]

I took the relevant changes from #641 about GitHub actions and combined them with the actions from Castle Core.

Right now I am having an issue with exit code 1 caused by test projects not availabe for a certain framework version.

[jonorossi]

@Toxantron I've marked your pull request draft. I've added a Gmail filter to star Castle tickets so they don't get lost in my inbox, but mention me if I don't respond in a couple of days.

[Toxantron]

@jonorossi I completed the action scripts for Windows and Linux. On Linux we run everything for net6.0 and on windows the net462 tests only. The successful runs and unit tests you can find here.

I kept the release script from @renemadsen and cleaned it up a little bit, but it is basically untested.

Let me know, what you think.

[Toxantron]

@jonorossi do you need anything else to merge this? I could test the release script under a different ID on our myget feed, still would not garantuee correct behavior for upstream.

With this being merged we could at least disable AppVeyor CI runs.

[jonorossi]

I've added a couple review comments. If you can get packages published to GitHub Packages I'll take a detailed look at the output to confirm they are what I expect.

[Toxantron]

I confirmed the release pipeline works and I have created packages for tags.

However using GITHUB_TOKEN causes issues when pushing multiple packages for the first time. Rerunning the same job creates the missing packages. Since we rebuild anyways this does not even cause issues with expired artifacts.

[jonorossi]

The AppVeyor package feed is for CI builds (i.e. every build), you don't have to tag them. See the readme:
https://github.com/castleproject/Windsor#nuget-preview-feed

Maybe we don't really need it anymore, and we should just tag pre-release packages more often publishing betas to nuget.org.

Since you've got that publishing working, leave it for now. I don't have time tonight to look at the package contents but I'll get to it over the next day or two, it's a great test for publishing to nuget.org from tags!

[Toxantron]

We could have both. Push CI packages to GitHub after every merge on main and push to nuget.org for tags.