Improve Heartbeat and SessionMonitor

During the upgrade from AWS Go SDK v1 to v2, the internal heartbeat implementation did not use enforce any kind of network timeout. Under specific circumstances, SessionMonitor would lock waiting for the Heartbeat to fail, and the lock would be released before the SessionMonitor callback would be called.

This releases fixes the problem by ensure automatic heartbeat's network calls never outlive their established duration, therefore release the internal mutexes to let the SessionMonitor callback to be triggered.

The original semantics in which expired locks won't trigger SessionMonitors remain the same (as in their original Java counterparts).

Add `HeartbeatRetries` to SendHeartbeat

v2.0.3

dynamolock/v2: adjust the linters to skip the use of generics

Bugfixes

• Modify timeUntilDangerZoneEntered to not manipulate the Lock semaphore in any sense, and force the Lock's semaphore use cases to be managed in all call sites explicitly.

v2.0.0

Updated internals to use Amazon latest SDKs

Add initial support for context.Context

Use *WithContext() calls for dynamoDB calls.

Fix bug in which consistency checks would derail lock retries

dynamolock: exercise LockNotGrantedError unwrap path

Addresses cirello-io/dynamolock#56

Fix bug in the Get call that would not return released locks.

dynamolock: fix Get call to succeed even with released locks

Fixes cirello-io/dynamolock#52

Fix documentation.

build(deps): bump github.com/aws/aws-sdk-go from 1.23.4 to 1.23.7

Bumps [github.com/aws/aws-sdk-go](https://github.com/aws/aws-sdk-go) from 1.23.4 to 1.23.7.
- [Release notes](https://github.com/aws/aws-sdk-go/releases)
- [Changelog](https://github.com/aws/aws-sdk-go/blob/master/CHANGELOG.md)
- [Commits](https://github.com/aws/aws-sdk-go/compare/v1.23.4...v1.23.7)

Signed-off-by: dependabot-preview[bot] <[email protected]>

Do not wrap LockNotGrantedError in error.errorString

dynamolock: not wrap LockNotGrantedError in error.errorString

This eases the error handling in the callers code. The old implementation had in information loss. It was not easy to check if the error was simple cased by someone else grapping the lock.

Fix race condition in Lock.IsExpired call

v1.2.0

dynamolock: add hikhvar to CONTRIBUTORS list