fix: use logical OR instead of bitwise OR in conflict resolver

[dentiny]

Summary

Replace bitwise OR (|) with logical OR (||) in check_update_config_txn to enable short-circuit evaluation when checking for conflicting UpdateConfig transactions.

Context

In conflict_resolver.rs, the condition checking whether two UpdateConfig transactions conflict uses | (bitwise OR) instead of || (logical OR). While both produce the same boolean result, | always evaluates both operands.
Using || short-circuits on the first true, skipping the unnecessary call to modifies_same_metadata when upsert_key_conflict already determined a conflict.

Test plan

• Existing tests pass (cargo test -p lance)

[github-actions]

ACTION NEEDED
Lance follows the Conventional Commits specification for release automation.

The PR title and description are used as the merge commit message. Please update your PR title and description to match the specification.

For details on the error please inspect the "PR Title Check" action.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!