DistributedLockTimeOutException not thrown when acquiring lock

[brnls]

As mentioned in this comment: #119 (comment)

When one of the job schedulers like the recurring job schedulers tries to acquire a lock and that times out due to another hangfire server holding the lock, hangfire makes a debug log because this is a normal and expected situation. See https://github.com/HangfireIO/Hangfire/blob/main/src/Hangfire.Core/Server/RecurringJobScheduler.cs#L428

Hangfire.PostgreSql doesn't throw an exception of this type when the lock times out which makes this bubble up farther and get logged as an error.

I have an application that sees this error logged regularly while running multiple instances of the hangfire server. It recovers and there is no impact, but it does create a lot of unnecessary error log noise.

Could Hangfire.PostgresSql adjust to throw an exception of this type? At the moment it looks like it is throwing PostgreSqlDistributedLockException. I don't know if the answer is to make that inherit DistributedLockTimeOutException because it looks like it is used for other purposes as well.

If an adjustment like this sounds reasonable, I can make a PR.