Adding Storage Backend Selection in host.json

[bachuv]

These changes allow customers to configure which storage backend they want their app to use (e.g. Azure Storage, MicrosoftSQL, or Netherite) with a new type attribute under durableTask/storageProvider in host.json (example below). The extension will register all storage backend services and then choose which one to use in the DurableTaskExtension constructor. Adding the ability to register all backends and then choose a storage backend allows us to deploy all storage backend packages through extension bundles.

The main changes in this PR are allowing the extension to register a collection of services through dependency injection, adding a Name property in IDurabilityProviderFactory, and choosing the DurabilityProvider by comparing a customers configured type with the Name property in the available IDurabilityProviderFactory implementations.

{
  "version": "2.0",
  "extensions": {
    "durableTask": {
      "storageProvider": {
        "type": "MicrosoftSQL",
        "connectionStringName": "SQLDB_Connection"
      }
    }
  }
}

Resolves #1666

Pull request checklist

• My changes do not require documentation changes
  • Otherwise: Documentation PR is ready to merge and referenced in pending_docs.md
• My changes should not be added to the release notes for the next release
  • Otherwise: I've added my notes to release_notes.md
• My changes do not need to be backported to a previous version
  • Otherwise: Backport tracked by issue/PR #issue_or_pr
• I have added all required tests (Unit tests, E2E tests)

[cgillum]

Looks good to me! Just a few nitpicks from my POV.

[ConnorMcMahon]

A few nits, but overall looks great!

[cgillum]

This looks good to me. Just a couple non-blocking comments.

[ConnorMcMahon]

LGTM!

[ConnorMcMahon]

I think the current tests need some tweaking.

[ConnorMcMahon]

The PR content is solid at this point! Just address some of the stylistic and naming suggestions before merging.