Fix CS1503: use named parameter to disambiguate ArgumentException overload.

SDK 10.0.300 introduced overload ambiguity between ArgumentException(string, string)
and ArgumentException(string, Exception?) when the message comes from a generated
resource that returns string?. Using paramName: resolves the ambiguity.

Author: tillig

src/Autofac.Extras.AggregateService/AggregateServiceGenerator.cs

@@ -47,7 +47,7 @@ public static object CreateInstance(Type interfaceType, IComponentContext contex
 
         if (!interfaceType.GetTypeInfo().IsInterface)
         {
-            throw new ArgumentException(AggregateServicesResources.TypeMustBeInterface, nameof(interfaceType));
+            throw new ArgumentException(AggregateServicesResources.TypeMustBeInterface, paramName: nameof(interfaceType));
         }
 
         var resolverInterceptor = new ResolvingInterceptor(interfaceType, context);