Throw specific errors when there's an issue either acquiring or releasing the lock about node-redlock HOT 1 OPEN

@vany0114 I also share your concern— throwing a ResourceLockederror when a vote goes against for a given instance and then handling such errors as this more generic ExecutionError is less than ideal.

I was playing around w/ adding this to the _execute event loop

        while (true) {
            const { vote, stats } = await this._attemptOperation(script, keys, args);
            attempts.push(stats);
            // The operation achieved a quorum in favor.
            if (vote === "for") {
                return { attempts };
            }
            if (vote === 'against') {
                throw new ResourceLockedError("Quorum Achieved. This instance lost vote")
            }

re-throwing as ResourceLockedError (which is also an exported class of this module) would then allow the consumer of this package to ignore these types of expected errors and only throw for other, unhandled errors.

@mike-marcacci is this something I should create a PR for? i do notice a large backlog of unreviewed PRs and am wondering if this would be a welcome addition

from node-redlock.