NuGet Pkg for v0.6.0 using GitHub Actions

[diogo-strube]

This PR is related to discussion #243 and is a 3 file contribution:

• nuget\jwt-cpp.nuspec contains all the descriptions of the NuGet package, including authors, and the path of files to be copied.
• nuget\jwt-cpp.targets automatically set up the "additional include directories" when the package is installed.
• .github\workflows\nuget.yml contains the GitHub Action to pack and pub the NuGet package.

Some context on the current approach:

• As the version is already tracked by committed files (as shown in 🏷️ Set version to 0.6.0 #208), I left the version explicit in the .nuspec file (instead of using an environment variable or secret).
• Publishing a NuGet pkg (to nugte.org) requires a token, the same was configured as a secret ${{ secrets.nuget_api_key }} in .github\workflows\nuget.yml.

[prince-chrismc]

Have you considered using https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows#release so that it will get pushed automatically?

I do like manual so we can test but less is more 😉

[Thalhammer]

I think manual is fine while we test, we can switch it later once we are more familiar with how it works.

[prince-chrismc]

Do we need access to the Nuget package to make an API token? I made an account with the same user name if you don't mind :)

[Thalhammer]

Yes, he needs to add one of us (or ideally both) as a owner for the package and we then need to create a secret here with the push token.

[prince-chrismc]

You are the only one who can add secrets AFAIK, I dont have access to the settings page where they can be added

(my evil genius plan to steal power is working muahahah 😈 )

[Thalhammer]

I dont have access to the settings page where they can be added

Guess I need to add them myself then 😈

[diogo-strube]

Added you both access as owners directly via NuGet.org so you can manage the package even before we publish the next one:

And the next commit will have you both added as owners in the .nuspec file, together with the version updated to a test one so you can experiment with running the workflow with your own token :)

[prince-chrismc]

Looks super good just a few questions

[diogo-strube]

@Thalhammer and @prince-chrismc, with the latest commit you should be ready to configure the secret and try running the workflow, it will generate a pre-release package "-dev0.2" that we can do a final validation before publishing the release package.

[Thalhammer]

@prince-chrismc Can you create a token for nuget ?
I can't cause I am not a co owner of the package but you seem to be now.

[prince-chrismc]

should be in you inbox :)