Create Schema.NET.Pending project for pending types

[Turnerj]

Will close #203

The core changes:

• New "Schema.NET.Pending" project
• All the C# source files for Schema.NET have been moved to a "common" folder and referenced by it and the new project
• Minor changes to the source generator to pull in a setting about including pending types

I don't think I have this quite right yet (particularly around pulling in the setting) but is the general gist of the changes required to support pending types.

Once #301 is in, it will make debugging this easier and then hopefully we can get full pending types supported!

[Turnerj]

A quick look suggests we might need another variation of our Values type with a different number of generic arguments. Will need to dig into this further.

[Turnerj]

I've got it working! The builds will take about 2x longer now (likely also making Visual Studio a little more sluggish) but we get the functionality we want.

[Turnerj]

Once we've got this in, should we release a new version (and thus the first version of Schema.NET.Pending)?

[Turnerj]

Just want to make sure before I create a new release that the NuGet key you've configured for the repo has the "Create new packages" permission. I've had issues before of not doing that and then manually having to remove tags/releases and re-running it.

[RehanSaeed]

Write permissions for GitHub packages are in the build:

I recently switched to using this least priviledge approach for all my repos and defaulted to read rights in settings:

Only downside is that autolabeller seems to have stopped working and I have no idea why:

release-drafter/release-drafter#869

[Turnerj]

Ahhhh, sorry, I meant permissions in NuGet.org itself. So when you have your API key in NuGet, you get a screen like this:

What I'm referring to is whether you have "Push new packages and package versions" or whether it is "Push new package versions". With our "Schema.NET.Pending" library, it will need that unless you want to upload the first package for it manually.

[RehanSaeed]

Oh I see. I have one key per project and get notified when they expire, so we won't have that problem.

[Turnerj]

Looks like we might have missed something. The Schema.NET.Pending package didn't push to NuGet and the one that pushed to GitHub Packages isn't correctly versioned... 🤔

[Turnerj]

I think the MinVerTagPrefix is what caused the issue. It is <MinVerTagPrefix>$(PackageId).</MinVerTagPrefix> which won't work anymore with two packages with two different names (unless you want to do two tags per release - one Schema.NET.<version> and another Schema.NET.Pending.<version>).

[RehanSaeed]

Fixed in #303. Will delete the tag and re-release. Annoying but required.

[Turnerj]

Cheers mate!