Support IServiceProvider access when registering DbContext

[aaronpowell]

Description

Adding overloads that allow you to provide a callback with access to the IServiceProvider when configuring a dbcontext.

Fixes #7016

Checklist

• Is this feature complete?
  • Yes. Ready to ship.
  • No. Follow-up changes expected.
• Are you including unit tests for the changes and scenario tests if relevant?
  • Yes
  • No
• Did you add public API?
  • Yes
    • If yes, did you have an API Review for it?
      • Yes
      • No
    • Did you add <remarks /> and <code /> elements on your triple slash comments?
      • Yes
      • No
  • No
• Does the change make any security assumptions or guarantees?
  • Yes
    • If yes, have you done a threat model and had a security review?
      • Yes
      • No
  • No
• Does the change require an update in our Aspire docs?
  • Yes
    • Is this introducing a breaking change?
      • Yes
        • Link to aspire-docs issue (please use this breaking-change template):
      • No
        • Link to aspire-docs issue (please use this doc-idea template):
  • No

Microsoft Reviewers: Open in CodeFlow

[eerhardt]

We should do this for all EF providers, not just 2 of them.

Also, we should be adding tests as well.

cc @sebastienros

[eerhardt]

This isn't going to work well because the 2 methods have the same signature, so if you call builder.AddNpgsqlDbContext("name"), the compiler won't know which one you mean.

To fix this, we will need to expand the existing method out into overloads without default parameters. Similar to #6929 and #4327.

[aaronpowell]

Done

[aaronpowell]

All EF providers are now covered in the PR.

I haven't added any new tests, so if you want test coverage expanded let me know what you're after