Skip refreshing orders locked for save

At least, Why @jsacksick

I checked Pipelines, it says `few arguments to function Drupal\commerce_order\OrderRefresh::__construct(), 4 passed` But actually i already but the 5th one and its there. There should some cache etc in the pipeline isn't it?

@emircanerkul: You're opening an issue without describing what issue you are trying to solve? How am I supposed to know what this is about?

@jsacksick, sorry my bad. I thought the title would be enough to describe the problem. Details are updated.

Retitling for clarity...
I think if we do this we should rely on the order storage... As we shouldn't hardcode the lock ID in multiple places...

So perhaps we need an isLockedForSave() method on the order storage but I'm a bit reluctant to commit this as this change will probably impact performance...
Also I believe we should negate the call?
Instead of $this->lockBackend->lockMayBeAvailable() we probably need !$this->lockBackend->lockMayBeAvailable() no?

I agree, it needs some refactoring to prevent hardcoding lock ID in multiple places.

Yes, it definitely affects performance but this is the Drupal way of locking. IDK maybe we need to switch commerce's locking system to that.

Regarding negating, yes you're right [done]. But the naming is weird, Instead of lockMayBeAvailable, I would prefer isLockable.

But the naming is weird, Instead of lockMayBeAvailable, I would prefer isLockable.
This is a Drupal core melthod, not Commerce method...

Yea, I know...