Register mocks as singletons

[xzxzxc]

Fixes #43

[tillig]

It seems like, since the "workaround" is basically to provide a singleton instance anyway... this seems like a reasonable fix.

Likely we'll need to release a major version since it'll be a breaking behavioral change, but that's fine.

[tillig]

One note about the unit test as an example.

[codecov]

Codecov Report

Patch coverage: 100.00% and no project coverage change.

Comparison is base (1eff21e) 93.96% compared to head (930fff6) 93.96%.

❗ Current head 930fff6 differs from pull request most recent head 472c54a. Consider uploading reports for the commit 472c54a to get more accurate results

Additional details and impacted files

@@           Coverage Diff            @@
##           develop      #46   +/-   ##
========================================
  Coverage    93.96%   93.96%           
========================================
  Files            3        3           
  Lines          116      116           
  Branches        20       20           
========================================
  Hits           109      109           
  Misses           5        5           
  Partials         2        2           

Impacted Files	Coverage Δ
src/Autofac.Extras.Moq/MoqRegistrationHandler.cs	94.02% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

[tillig]

Looks good, thanks! It will be a bit before I can get a release out with this, but the MyGet feed will have interim builds you can consume if you're in a rush.

[xzxzxc]

@tillig, Hi! Do you have plans to release this? MyGet is down, and I'm having trouble building my projects. Or could you create a prerelease version in NuGet, maybe?

[tillig]

Thanks for the reminder - let me see if I can get this today. Sorry for the delay!

[tillig]

6.1.1 just got pushed, should start showing up in NuGet shortly.

[xzxzxc]

@tillig, thank you!

BTW, previously you said that

Likely we'll need to release a major version since it'll be a breaking behavioral change, but that's fine.

Just curious, did you change your mind?

[tillig]

No, I just figured it was fixing a kind of bug, forgot about the major release part, incremented the bug release part, and called it a day. At some point we'll have to drop .NET 5 because it's no longer supported and that will also trigger a major release. Sorry for the confusion, day job is really kicking my ass in recent months so I'm just moving as fast as I can to get things done. Mistakes get made. 🤷