retry sql when connection from pool was stale
add Hub.IsDead flag to database
update QueuePartitionLocker to handle partitions locked by dead hubs
add CurrentHub as singleton

Conflicts:
	Druq.Hub/Messaging/IdempotencyService.cs
HubLifeSupport updates local cache of dead and active hubs
PartitionMaintenance clears dead hub message locks
add tests and fix bus for removing dead hub locks from messages
add logging
Merge pull request #57 from daptiv/fix-hub-life-support-perf

- [ ] @EEE3 please test
update current hub last ping

- keeps logs from looking wonky
remove unused ConsoleRunOptions

- it was misleading when i looked at it
we only need one thread at a time marking dead hubs.  but...

pinging will let as many threads as necessary perform the keep alive ping, just in case one sql connection is having issues and another one can get through
Merge pull request #58 from daptiv/optimize-life-support

Optimize life support
fix bug where new hub could be marked as dead incorrectly
Merge branch 'master' into 62093-Adding-Subsriber.Settings.OverRides
added in subscribermetadata tests