Adding github actions to generate nuget package of SharpNeat

[eramosr16]

• Basically create a Github action to create and publish a Nuget Package with the SharpNeat core library, the intent is to be able to use the library in broader experiments and applications including web projects, console apps, etc.

@colgreen Github by default is publishing to your internal Nuget Repository, we need to publish to Nuget (https://www.nuget.org), let me know if you want to create it or I can do it, I rather you keep the ownership though.

Let me know if you need further assistance.

[colgreen]

Hi. Thanks for your submission. I have now published the most recent version to nuget.org: https://www.nuget.org/packages/SharpNeat/4.1.0

I expect to only make one or two releases a year - changes in the main branch should be considered as ongoing development commits towards the next release, therefore I don't wish to auto publish from main, as it may not always represent fully working or tested code.

I will aim to publish future releases - I had gotten out of the habit as I didn't think there was much demand for it, but it's a small effort so there's no reason not to. It does mean I should follow semantic versioning rules from now on, i.e. a major version change will indicate one or more breaking changes, whereas up until now the major version has been more of a 'marketing' version number.

It was interesting to see how this would be done with a yaml workflow, but I have security concerns with registering a nuget.org API key inside github, also it's good practice to give the keys a limited lifetime and cycle them, which would be additional effort to maintain. It would be worth the effort it I wanted to publish frequently, but I prefer to do a small number of curated each releases a year instead.