[18.0][IMP] shopfloor_base: Allow changing the way locks are acquired

[grindtildeath]

This commit adds two new system parameters:

• shopfloor.lock.for_update.no_key: Can be defined with a True-ish value to use FOR NO KEY UPDATE in the select to acquire a lock on selected rows

• shopfloor.lock.for_update.no_wait: Can be defined with a True-ish value to use NOWAIT and raise an error instead of waiting for the lock to be acquired.

Note that NOWAIT keyword cannot be use in conjunction with SKIP LOCKED, hence, if skip_locked arg is used, the value of no_wait parameter will be ignored.

[OCA-git-bot]

Hi @simahawk, @guewen, @sebalix,
some modules you are maintaining are being modified, check this out!

[grindtildeath]

Logging testing on odoo shell:

>>> from odoo.addons.shopfloor_base.actions.lock import LockAction
>>> records = env["res.partner"].browse([1,2])
>>> action = LockAction(records)
>>> action.for_update(records)
2026-02-13 17:34:23,058 1 DEBUG demo_shopfloor odoo.addons.shopfloor_base.actions.lock: Trying to acquire  FOR UPDATE  lock on res_partner for IDs [1, 2] 
2026-02-13 17:34:23,059 1 DEBUG demo_shopfloor odoo.addons.shopfloor_base.actions.lock: Lock was acquired on res_partner for IDs [1, 2] in 0.0007 seconds 
True
>>> env.cr.rollback()
2026-02-13 17:34:29,714 1 DEBUG demo_shopfloor odoo.addons.shopfloor_base.actions.lock: Lock was released on res_partner for IDs [1, 2] 

[gurneyalex]

pre-commit is complaining. But LGTM otherwise