feat: Enable AOT-compatibility

[campersau]

• Enable IsAotCompatible
• Generate DockerModelsJsonSerializerContext with all docker API models which have JSON parameters, so query string only models are not added for JsonSerialization
• Add DockerExtendedJsonSerializerContext which includes types directly used by *Operations (this can be removed / merged with DockerModelsJsonSerializerContext when STJ source generator fails when defining the serializer context in 2 partial classes dotnet/runtime#99669 is available)
• Update reflection APIs with DynamicallyAccessedMembers attributes
• Update xunit to xunit.v3.aot.mtp-v2 4.0.0-pre.33 which is still in preview but required to actually test AOT.
• Use xunit.v3.mtp-v2 4.0.0-pre.33 for .NET 8.0 because xunit AOT only works from .NET 9 onwards.
• Cleanup preprocessor directives
• Change all IEnumerable responses to be IList for consistency (breaking change)
• Use generic QueryStringParameter to reduce reflection

fixes #88

[campersau]

Before (main)

Method	Mean	Error	StdDev	Allocated
CreateContainerRequestResponse	190.7 ms	107.9 ms	5.91 ms	34.55 KB
StartContainerRequestResponse	717.5 ms	371.3 ms	20.35 ms	47.59 KB

Docker.DotNet.dll 464 KB (475.648 Bytes)

After (AoT)

Method	Mean	Error	StdDev	Allocated
CreateContainerRequestResponse	185.8 ms	109.1 ms	5.98 ms	41.77 KB
StartContainerRequestResponse	702.5 ms	478.7 ms	26.24 ms	68.9 KB

Docker.DotNet.dll 3,01 MB (3.162.112 Bytes)

[HofmeisterAn]

FYI: I will need a few days for the review. I'm pretty busy this week.

[HofmeisterAn]

I'll do the review this weekend.

[campersau]

No worries. This currently uses a preview version of xunit aot. Stable release should be soon.

[HofmeisterAn]

Thanks, the PR looks good! I just have a few questions so I can understand a few things better.

[HofmeisterAn]

question: Do you think we can generate these? What about a separate C# generator or validation tool for the API 😬?

[campersau]

I am currently not sure what the best way is to automate this.

[HofmeisterAn]

Yes, difficult... What do you think about a test that uses reflection to check whether the return and parameter types of the API (interface) implementations are part of the context?

[campersau]

Or maybe we can write an analyser. Never done that from scratch but I can try. We need to now the generic type of MakeRequestAsync.
Not sure if a source generator would work because STJ also uses a source generator.

[HofmeisterAn]

We need to now the generic type of MakeRequestAsync.

Yea, that's right. My idea e.g. fails with (PluginInstallParameters vs. IList<PluginPrivilege>):

Docker.DotNet/src/Docker.DotNet/Endpoints/PluginOperations.cs

Lines 43 to 63 in 2f9b40f

	public Task InstallPluginAsync(PluginInstallParameters parameters, IProgress<JSONMessage> progress, CancellationToken cancellationToken = default)
	{
	if (parameters == null)
	{
	throw new ArgumentNullException(nameof(parameters));
	}
	if (parameters.Privileges == null)
	{
	throw new ArgumentNullException(nameof(parameters.Privileges));
	}
	var queryParameters = new QueryString<PluginInstallParameters>(parameters);
	var data = new JsonRequestContent<IList<PluginPrivilege>>(parameters.Privileges, DockerClient.JsonSerializer);
	return StreamUtil.MonitorStreamForMessagesAsync(
	_client.MakeRequestForStreamAsync(_client.NoErrorHandlers, HttpMethod.Post, $"plugins/pull", queryParameters, data, null, cancellationToken),
	progress,
	cancellationToken);
	}

Probably we need:

• MakeRequestAsync
• JsonRequestContent
• MonitorStreamForMessagesAsync

But we can also handle that in a follow-up PR if that's more convenient.

[HofmeisterAn]

I have one more topic, but aside from the open discussions, the PR looks good. We can also address some of those in a follow-up PR if you prefer.

PluginPrivilege[] covers the array response, but InstallPluginAsync and UpgradePluginAsync serialize an IList<PluginPrivilege>.

IList<PluginPrivilege> is a different closed type from PluginPrivilege[], so it needs its own JsonSerializable entry in the combined serializer context, right?

I belive the analyzer is a good idea 💡.

I think these are missing too (or we change them to arrays too):

// PluginOperations.InstallPluginAsync, UpgradePluginAsync
[JsonSerializable(typeof(IList<PluginPrivilege>))]
// PluginOperations.ConfigurePluginAsync
[JsonSerializable(typeof(IList<string>))]

// SecretsOperations.ListAsync
[JsonSerializable(typeof(IList<Secret>))]

// TasksOperations.ListAsync
[JsonSerializable(typeof(IList<TaskResponse>))]