Bump Autofac and Autofac.Extensions.DependencyInjection in /src/Miningcore

[dependabot]

Bumps Autofac and Autofac.Extensions.DependencyInjection. These dependencies needed to be updated together.
Updates Autofac from 8.0.0 to 8.1.0

Release notes

Sourced from Autofac's releases.

v8.1.0

What's Changed

• Optimized required member caching (#1415 - thanks @​SergeiPavlov!)
• Correctly handle polyfilled required infrastructure attributes by (#1421 - thanks @​DoctorVanGogh!)
• Improve memory management in registered services tracking (#1423 - thanks @​snaumenko-st!)
• Fix #1330: Generic decorators attached to generics that expose multiple service types should be handled properly (#1424)

Full Changelog: autofac/Autofac@v8.0.0...v8.1.0

Commits

• b222d0f Use latest SDKs for build.
• 4106a2d Semver 8.0.1 => 8.1.0 for dependency update.
• a8f398f Update dependencies to latest.
• 5aeecc7 Semver 8.0.0 => 8.0.1 for bug fixes.
• 4059546 Merge pull request #1424 from autofac/feature/generic-decorator
• c12d527 Merge pull request #1423 from snaumenko-st/tracker-memory-leak
• caa3e04 Add a resolved/compatible service parameter to decorator resolutions.
• 488294e Merge pull request #1421 from DoctorVanGogh/fix-required
• bb9e961 Replaced ConcurrentBag with ConcurrentQueue. It's causing memory leaks if lef...
• e68c1b8 use polyfill copied from dotnet runtime
• Additional commits viewable in compare view

Updates Autofac.Extensions.DependencyInjection from 8.0.0 to 10.0.0

Release notes

Sourced from Autofac.Extensions.DependencyInjection's releases.

v10.0.0

Breaking Changes

All instance dependencies are now considered ExternallyOwned which means if you register an object instance in the dependency injection container through this package, when you dispose of the container it will not dispose of the provided instance. This is different than default Autofac behavior. Autofac normally assumes control of registered instances, where the Microsoft DI container does not. This change only affects instances registered using the Microsoft syntax and then populated into Autofac; it does not change the underlying Autofac container.

public class Startup
{
  public void ConfigureServices(IServiceCollection services)
  {
      // The instance `item` here WILL NOT be disposed when the container is disposed
      // because it's registered using Microsoft syntax and will be imported into Autofac.
      var item = new MyDisposableItem();
      services.AddSingleton(item);
  }
public void ConfigureContainer(ContainerBuilder builder)
{
// The instance item here WILL be disposed when the container is disposed
// because it's registered using Autofac syntax directly with Autofac.
var item = new MyDisposableItem();
builder.RegisterInstance(item);
}
}

Additional Changes

• Optimization for reflection-activated components to avoid adding a parameter in the resolve path if possible. (@​alistairjevans #119)
• Updated Autofac dependency to 8.1.0.

Full Changelog: autofac/Autofac.Extensions.DependencyInjection@v9.0.0...v10.0.0

v9.0.0

Breaking Changes

• Removed support for netcoreapp3.1 and net5.0
• Updated minimum core Autofac to 8.0.0, which includes similar target support updates. See release notes for core Autofac.

Additional Changes

• Added keyed service support (IKeyedServiceProvider, IServiceProviderIsKeyedService, support for AnyKey) to match Microsoft.Extensions.DependencyInjection feature updates for .NET 8. (#115)

Full Changelog: autofac/Autofac.Extensions.DependencyInjection@v8.0.0...v9.0.0

Commits

• f2170d3 Dispose tracker in tests before it loses scope.
• 344c14b Update all dependencies/build frameworks.
• eb20702 Merge pull request #120 from autofac/external-dependency-switch
• ecec468 Bump major version.
• 4110c93 Switch singletons to be externally owned.
• dc03f10 Merge pull request #119 from autofac/bug/keyed-middleware-performance
• a690c3c Add additional test, and comments for the delegate perf choice.
• 8e83d8c Consider additional activator types.
• fa4b37e Reword a note.
• ed2188e Simplify back to a single middleware, added at component registration level r...
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.