Description

This PR proposes adding withLockedRow() to CodeIgniter\Model.

It is a small helper for cases where we need to reload a single row inside a transaction, lock it for update, and then run some code with that locked row.

$result = $accountModel->withLockedRow($id, static function (object $account, $model): bool {
    $account->balance -= 100;

    return $model->save($account);
});

This gives users a clear path for single-row mutations that need a pessimistic lock, without having to remember to manually wrap lockForUpdate() in a transaction each time. It does not add new lock behavior; it only scopes the existing transaction and lock APIs together.

The method uses the existing transaction() helper and Query Builder lockForUpdate(), so it follows the same transaction and driver-specific locking behavior.

A few details:

• if the row is not found, the callback is not called and null is returned
• if the transaction cannot start or fails without an exception, false is returned
• if the callback throws, the transaction is rolled back and the exception is rethrown
• existing Model query constraints, like where() and withDeleted(), are applied
• Model find callbacks are not run for the locked reload, so they cannot skip the actual database read

This does not add new lock modes or special driver handling. Unsupported lock combinations still throw the same exceptions as lockForUpdate().

Checklist:

• Securely signed commits
• Component(s) with PHPDoc blocks, only if necessary or adds value (without duplication)
• Unit testing, with >80% coverage
• User guide updated
• Conforms to style guide