Revert http resilience upgrade

[eerhardt]

There is a breaking change with Grpc clients in this version. See dotnet/extensions#4924

InvalidOperationException: The ConfigureHttpClient method is not supported when creating gRPC clients. Unable to create client with name 'BasketClient'.
Grpc.Net.ClientFactory.Internal.GrpcCallInvokerFactory.CreateInvoker(EntryKey key)
System.Collections.Concurrent.ConcurrentDictionary<TKey, TValue>.GetOrAdd(TKey key, Func<TKey, TValue> valueFactory)
Grpc.Net.ClientFactory.Internal.GrpcCallInvokerFactory.CreateInvoker(string name, Type type)
Grpc.Net.ClientFactory.Internal.DefaultGrpcClientFactory.CreateClient<TClient>(string name)
Microsoft.Extensions.DependencyInjection.GrpcClientServiceExtensions+<>c__DisplayClass7_0<TClient>.<AddGrpcHttpClient>b__2(IServiceProvider s)
Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor<TArgument, TResult>.VisitCallSiteMain(ServiceCallSite callSite, TArgument argument)
Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitDisposeCache(ServiceCallSite transientCallSite, RuntimeResolverContext context)
Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor<TArgument, TResult>.VisitCallSite(ServiceCallSite callSite, TArgument argument)
Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitConstructor(ConstructorCallSite constructorCallSite, RuntimeResolverContext context)
Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor<TArgument, TResult>.VisitCallSiteMain(ServiceCallSite callSite, TArgument argument)
Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitRootCache(ServiceCallSite callSite, RuntimeResolverContext context)
Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor<TArgument, TResult>.VisitCallSite(ServiceCallSite callSite, TArgument argument)
Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.Resolve(ServiceCallSite callSite, ServiceProviderEngineScope scope)
Microsoft.Extensions.DependencyInjection.ServiceProvider.CreateServiceAccessor(ServiceIdentifier serviceIdentifier)
System.Collections.Concurrent.ConcurrentDictionary<TKey, TValue>.GetOrAdd(TKey key, Func<TKey, TValue> valueFactory)
Microsoft.Extensions.DependencyInjection.ServiceProvider.GetService(ServiceIdentifier serviceIdentifier, ServiceProviderEngineScope serviceProviderEngineScope)
Microsoft.Extensions.DependencyInjection.ServiceLookup.ServiceProviderEngineScope.GetService(Type serviceType)

Microsoft Reviewers: Open in CodeFlow

[radical]

Would it be possible to also add an explicit unit test for this, so it doesn't we don't depend on running the actual app to catch it?

[eerhardt]

Would it be possible to also add an explicit unit test for this, so it doesn't we don't depend on running the actual app to catch it?

What exactly do you imagine us testing? This is a break between Http.Resilience (in dotnet/extensions) and gRPC client (which we don't own). .NET Aspire doesn't do anything with gRPC by default, we just happen to use it in one of our "playground apps".

[radical]

Would it be possible to also add an explicit unit test for this, so it doesn't we don't depend on running the actual app to catch it?

What exactly do you imagine us testing? This is a break between Http.Resilience (in dotnet/extensions) and gRPC client (which we don't own). .NET Aspire doesn't do anything with gRPC by default, we just happen to use it in one of our "playground apps".

ah, ok. nvm then!

[joperezr]

FWIW, the issue will be fixed in extensions for 8.2, either by fixing the code that introduced the regression or by reverting the change entirely.

[eerhardt]

FWIW, the issue will be fixed in extensions for 8.2, either by fixing the code that introduced the regression or by reverting the change entirely.

We need to fix this sooner because our playground/eShopLite app is broken in main.