Fix for #127 Is not properly using TaskHubName

[bhugot]

Fixed #127 Durability factory when calling for a client is using default TestHubName or DurableTaskOption HubName instead of using the specified TaskHub

[cgillum]

Thanks for this PR! I few questions/comments:

[bhugot]

Hello @cgillum I reworked a bit the test so that we also use custom schema.

[bhugot]

Hello @cgillum any news on this?

[cgillum]

Thanks for the ping, and so sorry for dropping the ball on this PR. My only remaining ask is if we can drop a few things that I don't think are fully necessary. After that, I'm good to accept this.

[bhugot]

All good for me @cgillum

[bhugot]

@cgillum I fixed the test it was timeout due to purge but it's not required in multitenancy tests

[cgillum]

It looks like there might be a test concurrency issue now that we have multiple integration test classes . Here's the error from the CI:

Content root path: /home/runner/work/durabletask-mssql/durabletask-mssql/test/DurableTask.SqlServer.AzureFunctions.Tests/bin/Debug/net6.0/
  Failed DurableTask.SqlServer.AzureFunctions.Tests.WithoutMultiTenancyCoreScenarios.MultiInstanceQueries [1 ms]
  Error Message:
   System.Net.Sockets.SocketException : Address already in use

The solution mentioned here might be good to look into.

[bhugot]

Thx for the tips @cgillum was looking at it. could you rerun I hope attribute on CoreScenario is going to work with inheritance

[bhugot]

Great

[cgillum]

Alright, everything looks good. Thank you for this contribution!