[Eslint Plugin] Fix enforce-update-with-where false positive when .from() precedes .where()

[LeSingh1]

Closes #5612.

The enforce-update-with-where rule reports an update without where when .from() appears before .where() in the chain, for example:

await tx
  .update(table)
  .set({ ... })
  .from(sql`(VALUES ...) AS v(...)`)
  .where(eq(table.id, v.id));

The rule decides whether to report on the .set() MemberExpression by checking a module-level lastNodeName variable that is updated each time a MemberExpression is visited. ESLint visits MemberExpression nodes from the outermost call inward, so for the chain above the visit order is .where, then .from, then .set, then .update. By the time .set is visited, lastNodeName is "from" rather than "where", so the rule fires even though .where is present in the same chain.

The fix replaces the visit-order heuristic with a small AST walk that follows the surrounding CallExpression and MemberExpression nodes upward from the .set() MemberExpression, and reports only when no later chained call uses the name where. Behavior for chains without a trailing .from() is unchanged.

Tests:

Added two valid cases to tests/update.test.ts covering .from() before .where(), with and without a trailing .returning(). Both fail on main and pass with the fix. All 113 existing rule tests still pass.