Bug: `@eslint-react/set-state-in-effect` does not ignore calls in `.finally()` blocks in useCallback

React version: 18.2.0

Steps To Reproduce

1. Call a setter in a .finally() block inside a useCallback, where the callback is called in a useEffect.
2. The setter gets flagged as being a synchronous call in an effect.

Link to code example: https://codesandbox.io/p/devbox/rcl9wz
You can run npx eslint in the terminal and it shows the false positive. src/index.tsx shows the actual code.

Pasting it here for convenience too:

import { useCallback, useEffect, useState } from "react";

const Component = () => {
  const [state, setState] = useState(0);
  const callback = useCallback(() => {
    new Promise(() => {}).finally(() => {
      setState(1); // BUG: has a warning
    });

    new Promise(() => {}).then(() => {
      setState(1); // does not have a warning
    });
  }, []);

  useEffect(() => {
    new Promise(() => {}).finally(() => {
      setState(1); // does not have a warning
    });

    callback();
  }, [callback]);

  return state;
};
export default Component;

The current behavior

Warning on line 7, which is a setter call inside a .finally() inside a useCallback the result of which is called in a useEffect, but not on a setter call inside a .then() that's otherwise identical, and not in a .finally() that's not in a useCallback.

The expected behavior

There should be no warning, it's the same case as with the .then() that shows no warning.