[BUG] Splat.Microsoft.Extensions.DependencyInjection never disposes the service locator

[calebkiage]

Describe the bug
The .NET ServiceProvider can dispose services with managed resources according to the Disposal of Services docs, but this only works if the service provider instance is also disposed properly. However, the MicrosoftDependencyResolver class:

splat/src/Splat.Microsoft.Extensions.DependencyInjection/MicrosoftDependencyResolver.cs

Lines 253 to 265 in a7aae8b

	public void Dispose()
	{
	Dispose(true);
	GC.SuppressFinalize(this);
	}
	/// <summary>
	/// Disposes of the instance.
	/// </summary>
	/// <param name="disposing">Whether or not the instance is disposing.</param>
	protected virtual void Dispose(bool disposing)
	{
	}

never disposes the container. This affects services that need to do work to clean up resources when they're disposed.

Steps To Reproduce
Provide the steps to reproduce the behavior:

1. Create a ServiceCollection
2. Register an IDisposable service and add a log to the dispose method
3. Call ServiceCollection.UseMicrosoftDependencyResolver on your service collection
4. Use an instance of the service
5. Exit the application
6. The message will not be displayed.

Expected behavior
I expect that the service provider should be disposed when the container is disposed

Screenshots
If applicable, add screenshots to help explain your problem.

Environment(please complete the following information):

• OS: Windows
• Version: 11
• Device: PC

Additional context
When I use a custom class that disposes the ServiceProvider in use and also manually call:

if (Locator.Current is IDisposable d)
{
    d.Dispose();
}

The service is disposed correctly.

[Snailya]

Meets the same problem.
When calling the Locater.Current.GetService to get the service, it does not call something like ServiceProviderEngineScope.CaptureDisposable to check if the service is IDisposable, so it is not disposed after the scope is disposed.