feat: raise error when advisory lock cannot be acquired within configured timeout

[Farjaad]

Overview

This PR introduces an :advisory_lock_timeout_seconds configuration option that triggers an error when an advisory lock cannot be obtained within the specified time limit.

Motivation

We experienced jobs that would wait for several minutes executing SELECT GET_LOCK until Sidekiq terminated them. This created queue blockages and led to significant job backlogs. Implementing a timeout enables jobs to fail quickly and retry during periods of lower contention, ultimately completing successfully.

Example Usage

class Tag < ApplicationRecord
  has_closure_tree advisory_lock_timeout_seconds: 30
end

Behavior

When advisory_lock_timeout_seconds is configured, a WithAdvisoryLock::FailedToAcquireLock exception is raised if the lock cannot be secured within the designated timeframe, creating explicit failure handling for lock contention scenarios.

Without this configuration, the system maintains the default behavior of waiting indefinitely until lock acquisition.

Implementation Details

• Introduces advisory_lock_timeout_seconds configuration option
• Invokes with_advisory_lock! with lock parameters when advisory_lock_timeout_seconds is specified

Backward Compatibility

The advisory_lock_timeout_seconds option defaults to nil, and with_advisory_lock! is only invoked when a non-null value is supplied.